Resources · Zapier integration

NutriBot Zapier integrationAutomate NutriBot with Zapier.

The NutriBot Zapier integration gives you 2 triggers, 0 actions and 0 search steps. Both triggers are polling ones: Zapier checks NutriBot on a timer set by your plan, then hands each new customer or meal order to your other apps.

See the 2 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the NutriBot Zapier integration does for you

It lets the customers and orders of your meal prep business flow out of NutriBot into the tools you already use. A trigger (the NutriBot event that starts the automation) watches new customers and new orders. The action (the step that writes something for you) always lives in another app.

A kitchen list that fills itself. New Order drops each order into a shared sheet, so whoever plans tomorrow's prep reads one list instead of scrolling through NutriBot.

A welcome that never gets skipped. New Customer passes each new account to your email tool, so the first message goes out without anyone thinking about it.

A CRM that knows your regulars. Both triggers together feed your CRM with who signed up and who ordered, which makes reorder campaigns possible.

Each of these runs on its own two-step Zap, which the free plan covers on its own.

What Zapier does not do here: it cannot write into NutriBot or look anything up there. No order, no customer gets created or changed from a Zap. And because both triggers poll, an order is not instant: on the free plan it can wait up to 15 minutes. If you are weighing other tools, n8n vs Zapier and Make vs Zapier set Zapier side by side with each of them.

Vocabulary

Zapier vocabulary in one minute

Seven words come back on this page. Here they are in plain English.

Zap
The automation you build in Zapier: one trigger, then one or more actions that run every time that trigger event happens.
Trigger
The NutriBot event that starts the Zap, such as a new order. Once the Zap is switched on, Zapier waits for it.
Action
What the Zap does once started: the step that writes, sends or moves something for you, here always in another app.
Task
The unit Zapier bills: one action your Zap completes successfully. Your plan counts those and nothing else.
Polling trigger
A trigger Zapier checks on a timer: it asks the app for new items at a fixed interval. Both NutriBot triggers work this way.
Filter
A step that lets the Zap carry on only when the incoming data meets the condition you set, and stops it the rest of the time.
Connection
Your NutriBot account, linked to Zapier one time, then reused by every step in every Zap that reads NutriBot data.
Cost

What a NutriBot Zap really costs

Zapier bills tasks, and only actions create them. NutriBot brings only triggers, so the count happens in your other apps.

  • Trigger0 tasks
  • Successful action1 task
  • Failed action0 tasks
  • Free plan100 tasks a month, two-step Zaps
  • Premium appNo

The trigger never costs a task, and neither does Zapier checking NutriBot, however often it looks. Each action that succeeds counts once; one that fails counts nothing. The free plan gives 100 tasks a month, Zaps of two steps, and a check every 15 minutes. A filter or a second action makes the Zap multi-step, which needs a paid plan. NutriBot is not a premium app. The grid below sets how often Zapier checks, and it applies to both NutriBot triggers.

Connect

Connect your NutriBot account in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. A dialog opens with a search box. Before you go further, check that you can sign in to NutriBot and that you can see the customers and orders the Zap should follow.

  2. 02

    Pick NutriBot

    Type NutriBot in the search box, select it in the list, then click Add connection. Zapier opens a new tab where NutriBot asks for your usual login to finish the link.

  3. 03

    Sign in and grant access

    Log in to NutriBot in that tab and allow Zapier to reach the account. The connection then sits on your Apps page, and every Zap that uses NutriBot reuses it, so you do this once per account.

First Zap

Your first Zap: every order on the prep list

GoalAdd each new NutriBot order that matches your rule to a Google Sheets prep list.

  1. 01

    Create the Zap and pick the trigger

    Start a new Zap, choose NutriBot as the app and New Order as the event, then select your connection. This trigger polls, so it runs on the interval of your plan.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent orders of your account. Pick a real one: its fields are what you will map into the sheet.

  3. 03

    Add the filter

    Click the plus icon, choose Filter, then set the field, the rule and the value. Use a text rule on text and a number rule on numbers, or it never passes. The filter makes this a paid, multi-step Zap.

  4. 04

    Add the action in your sheet

    Add Google Sheets as the next app, pick your prep list and map the order fields into the columns. This step costs one task each time it succeeds.

  5. 05

    Test, then publish

    Test the action and read what Zapier returns before going further. Then click Publish. From now on, each new order lands in the sheet after the next check.

Triggers

NutriBot triggers: two polling events

2 events start a Zap when something happens in NutriBot. Zapier checks for them at the interval your plan allows.

1

New Customer

Polling trigger

In Zapier“Triggers when a new customer is created.”

Spots each customer account newly created in NutriBot and passes it on, so your mailing list and your CRM grow with your client base.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
add the new customer to your email tool and send a welcome message the day they sign up, without anyone typing it.
Watch out
Zapier remembers which customers it has already seen, so the same account never starts the Zap twice.
2

New Order

Polling trigger

In Zapier“Triggers when a new order is created.”

Picks up every order placed in NutriBot, which makes it the natural starting point for kitchen, delivery or bookkeeping automations.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
add each order to the prep sheet the kitchen reads, or send the customer a confirmation from your own mailbox.
Watch out
after a large import of orders, Zapier may receive a huge batch at once and hold it back with its flood protection.
When it breaks

When a NutriBot Zap breaks

Zapier links no help article to NutriBot, so the cases below are the general ones, applied to a meal prep business.

Most surprises come from timing and volume, not from the connection. If a Zap stops for no clear reason, the Zapier troubleshooting page is the next place to look.

  • No backlog when you publish

    A Zap only reacts to what happens after you switch it on. Customers and orders already in NutriBot stay out; moving them is a separate job.

  • Orders that seem late

    Both triggers poll. On the free plan, Zapier checks every 15 minutes, so an order can sit that long before the Zap runs. A paid plan shortens the wait.

  • Each item starts the Zap once

    Zapier keeps track of what it has already seen, so the same order never starts the Zap twice, which keeps your sheet free of duplicates.

  • Bulk imports and flood protection

    Importing many customers or orders at once can hand Zapier a huge batch in one go, and its flood protection may then hold those items back.
Need help

Need help automating NutriBot with Zapier?

A person reads every message.

FAQ

NutriBot and Zapier: common questions

01Is the NutriBot Zapier integration free?
Yes, it works on the free plan, because NutriBot is not a premium app. That plan gives 100 tasks a month, Zaps of two steps (one trigger, one action) and a check every 15 minutes. The limit shows up when you want more: a filter, a second action or a search step turns the Zap into a multi-step one, which needs a paid plan. You also need your own NutriBot account to connect.
02How many tasks does a NutriBot Zap use?
Nothing on the NutriBot side: both operations are triggers, and triggers never cost a task, however often Zapier checks. What counts is the action in the next app, one task each time it succeeds and none when it fails. A Zap that adds each order to a sheet costs one task per order. A Zap that also emails the customer costs two tasks per order, and needs a paid plan.
03Do NutriBot triggers run in real time?
No. Both NutriBot triggers are polling triggers: Zapier goes to NutriBot at a fixed interval and keeps only what is new. On the free plan that interval is 15 minutes, on Professional 2 minutes, on Team and Enterprise 1 minute. The type comes from the app itself and cannot be changed in the editor. On paid plans, you can also run a check by hand from the editor when you are testing.
04What does it take to connect NutriBot to Zapier?
A NutriBot account you can sign in to, with access to the customers and orders the Zap will follow. From the Apps page in Zapier, click + Add connection, search for NutriBot, confirm with Add connection, then sign in to NutriBot in the new tab and grant access. The connection is saved once and reused by every Zap that touches NutriBot, so you never repeat it. Check your own access in NutriBot before you start, too.
05Why does a NutriBot Zap not pick up old orders?
Because a Zap only reacts to what happens after it is published. Orders and customers already in NutriBot are never replayed, and moving that history is a separate job. Zapier also remembers what it has already seen on a polling trigger, so an order that came through once will not come through again. If a brand new order seems missing, wait for the next check before assuming something broke, then run the trigger test again.
06What if the NutriBot operation you need does not exist?
Then Zapier cannot do it with NutriBot today. The integration only listens to two events, new customers and new orders. It has no action and no search step, so nothing can be created, edited or looked up in NutriBot from a Zap. Those changes stay manual. A practical middle ground is to let a trigger alert the right person, who then acts in NutriBot. Another option is to check whether another automation tool reaches that operation.
07Zapier, Make or n8n for NutriBot?
It depends on your criteria, not on a winner. Zapier gives a quick start: two triggers and a free plan that covers a two-step Zap, with a check every 15 minutes. If the delay matters, the interval of each plan becomes the deciding factor. If your workflow chains many steps per order, task billing weighs more, and pricing models and hosting are worth comparing. Check what each tool exposes for NutriBot before choosing.
Same platform

Other docs you might need on this stack.

Browse all integrations