- Home
- Resources
- Integrations
- OrderOut
OrderOut Zapier integrationAutomate OrderOut with Zapier.
The OrderOut Zapier integration comes down to 1 trigger, 0 actions and 0 searches: New Order, which passes each delivery order your restaurant receives to the rest of your tools. It is instant, so the Zap starts right away, even on the free plan.
Verified Trustpilot reviews · AI, automation & growth agency
What the OrderOut Zapier integration is good for
OrderOut gathers the orders coming from delivery platforms such as Uber Eats, Postmates or DoorDash, plus Wix, and feeds them into your till system. Connected to Zapier, it can also hand each of those orders to other apps. The flow goes one way: OrderOut sends, nothing comes back.
Three results justify the setup. A sales log across every platform: New Order followed by a spreadsheet action keeps one list of delivery orders, whichever platform they came from. A kitchen or manager who hears about orders: the same trigger feeding a chat or email action alerts whoever needs to know, beyond the till. Guests who land in your customer list: each order can create or update a contact in the tool you use for loyalty or marketing.
What Zapier does not do for OrderOut matters as much. There is no action, so no Zap can accept, change or cancel an order in OrderOut. There is no search, so a Zap cannot look up an older order. And the only event is a new order: nothing reports when an order is updated later. In short, OrderOut is where your Zaps start, never where they end, and every flow has to be designed with that in mind. Before you commit, the Zapier review and n8n vs Zapier are one click away.
Zapier vocabulary in one minute
Eight words are enough to read this page. Each is explained once here, then used without a reminder.
- Zap
- The automation you build in Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event that starts the Zap. OrderOut offers exactly one: a new order received for one of your restaurants.
- 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. The allowance on your plan is counted in tasks.
- Instant trigger
- A trigger the app reports itself, the moment the event happens, so nothing waits for a scheduled check. New Order is one.
- Polling trigger
- A trigger Zapier checks on a timer, asking the app for new items at a fixed interval. OrderOut has none.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action or a filter turns a Zap into one, and it then needs a paid plan.
What an OrderOut Zap really costs
The trigger never costs a task, and OrderOut is not reserved for paid plans: it works from the free plan. What you pay for is what happens in the other apps.
- New Order0 tasks
- Successful action1 task each
- Failed actionnot counted
- Free plan100 tasks a month, two-step Zaps
Each action that succeeds counts as one task, and an action that fails is not counted against your plan. The free plan gives 100 tasks a month and builds two-step Zaps: New Order plus exactly one action. Add a second action or a filter and the Zap becomes multi-step, which needs a paid plan. The interval grid below concerns polling triggers only, so New Order never waits on it, whichever plan you are on.
Connect your OrderOut account in three steps
- 01
Open the Apps page
In your Zapier account, open the Apps page and click + Add connection. A connection is your OrderOut account linked to Zapier once, then reused by every Zap that listens to it.
- 02
Find OrderOut
Search for OrderOut in the dialog, select it, then click Add connection. You need an OrderOut account, plus access to any restaurant you do not own yourself but want the Zap to watch.
- 03
Sign in and allow access
OrderOut opens in a new tab. Sign in with the account that manages your restaurants, then grant Zapier access. The connection now shows up whenever a Zap starts with New Order.
Your first Zap: log and announce each delivery order
GoalEach new OrderOut order becomes a row in a sheet, then a message to the team on shift.
- 01
Pick the trigger
Start building the Zap, choose OrderOut as the app and New Order as the event that starts it, select your connection, then pick the Restaurant to follow.
- 02
Test on real orders
Run the trigger test. Zapier brings back the three most recent orders of the connected account, so the next steps are mapped on a real order, not a sample.
- 03
Add the sheet row
Pick Google Sheets as the action app and map the order details you want to keep into the columns of your sheet, one column per detail.
- 04
Add the message
Add Slack as a second action and write the message with details from the order. Two actions make this a multi-step Zap, so it needs a paid plan.
- 05
Test, then publish
Test each step once and read what came back before going further. When everything looks right, publish the Zap to switch it on.
The OrderOut trigger
1 event starts a Zap when something happens in OrderOut, and one of them is instant: the app calls Zapier straight away, whatever your plan.
New Order
Instant triggerIn Zapier“Triggers when a new order is by food delivery service.”
A delivery platform sends an order to your restaurant through OrderOut, and the Zap starts with that order in hand. It is the only door OrderOut opens to Zapier, so every automation built on this app begins here, whichever platform the guest ordered from.
When an OrderOut Zap breaks
Zapier attaches no help article to OrderOut, and no limit specific to the app is documented. The cases below are the general ones that hit any Zap, plus the one field this trigger requires.
With a single instant trigger there is little to tune, so breakdowns come from setup, timing and plan limits. For anything outside these cases, the Zapier troubleshooting page is the next stop.
Past orders never arrive
A Zap only reacts to what happens after it is switched on. Orders received before publication are not picked up, and moving that backlog is a separate job.No restaurant to pick
New Order requires a Restaurant. If the connected account does not manage the restaurant you want, the trigger cannot be set, so reconnect with the right account.A sudden flood held back
When a trigger returns a huge batch at once, after a bulk import or a migration for instance, Zapier's flood protection can hold it back.
Need help automating OrderOut with Zapier?
A person reads every message.



