OctoTable Zapier integrationAutomate OctoTable with Zapier.
The OctoTable Zapier integration gives you 3 triggers and 2 actions, no search. It watches new, updated and cancelled bookings in your restaurant or bar, and it can create or cancel a reservation for you. Here is what it does, what it costs and where it breaks.
Verified Trustpilot reviews · AI, automation & growth agency
What the OctoTable Zapier integration actually does
Connecting OctoTable to Zapier means your reservation book stops living on its own. When a guest books, changes or cancels a table, Zapier can pass that booking to another tool. In the other direction, a booking that starts somewhere else can land in OctoTable as a proper reservation, without anyone retyping it.
Three results come up again and again. First, a live log of every booking: New Reservation as the trigger, a row in a shared spreadsheet as the action, and your floor manager reads tonight's covers without opening OctoTable. Second, a clear view of cancellations: Reservation Cancelled feeds a list or a channel, so the team sees freed tables at the next check. Third, bookings that arrive through a form or an event tool become real OctoTable reservations through the New Reservation action, with the guest's name, email, party size, day and hour.
Now the honest part. Every OctoTable trigger works by polling, so nothing here is instant: Zapier checks on a timer that depends on your plan. There is no search step either, which means a Zap cannot look up an existing booking before acting on it. And there is no action to edit a booking: you can create one or cancel one, nothing in between. If the edit matters, the workaround is to cancel and create again, with two actions and a paid plan.
Not sure Zapier is the right tool for a restaurant setup? The n8n vs Zapier and Make vs Zapier comparisons lay out the criteria (price model, hosting, step limits) without picking a winner for you.
Zapier vocabulary in one minute
Seven words cover everything on this page. Each one is explained once, here, and used as is afterwards.
- Zap
- The automation you build: one trigger, then one or more actions that run each time that trigger event happens.
- Trigger
- The event that starts the Zap, such as a new OctoTable booking. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something on your behalf.
- Task
- The unit Zapier bills. One task is one action that completes successfully; your plan counts those.
- Polling vs instant
- A polling trigger is checked on a timer for new items. An instant one is reported by the app the moment it happens.
- Filter
- A step that lets the Zap continue only when the incoming data meets your condition, and stops it otherwise.
- Search step
- A step that looks up something already stored in an app so later steps can use it. OctoTable offers none.
What it really costs in tasks
OctoTable is not a premium app, so it works on the free Zapier plan. The bill is counted in tasks, and only completed actions count.
- Free plan100 tasks per month
- Steps per Zap on Free2: one trigger, one action
- Premium appNo
- Trigger cost0 tasks
The trigger never costs anything, and neither do the checks Zapier runs to spot new bookings, however often they happen. Each action that goes through counts as one task; an action that fails is not counted. A Zap with three actions uses three times what a one-action Zap uses. The free plan gives you 100 tasks a month and unlimited Zaps, but only two steps per Zap. Add a filter (say, only parties of six or more) or a second action and the Zap becomes multi-step, which needs a paid plan.
Connect your OctoTable account
- 01
Open your connections
In Zapier, go to the Apps page of your account and click + Add connection. A connection is your OctoTable account linked once, then reused by every step that touches OctoTable.
- 02
Pick OctoTable
Type OctoTable in the search box of the dialog, select it, then click Add connection. A new tab opens on the OctoTable side. You need an OctoTable account, with access to the venue whose bookings you want to automate.
- 03
Sign in and grant access
Log in to OctoTable in that tab and allow Zapier to reach your account. Once the tab closes, the connection appears in your list and every OctoTable step in every Zap can use it.
Your first Zap: log every OctoTable booking in a sheet
GoalEach new OctoTable reservation becomes a row in a shared spreadsheet the team can read.
- 01
Create the Zap
From the Zapier editor, start a new Zap. Choose OctoTable as the app and New Reservation as the event that starts everything.
- 02
Connect and test the trigger
Select your OctoTable connection, then run the test. Zapier brings back the three most recent bookings of the account, so you map fields from a real one.
- 03
Add an optional filter
To keep only big tables, add a filter on the guest count. Remember the rule types: pick a number rule for a number. This step makes the Zap multi-step, so a paid plan.
- 04
Add the action
Pick the spreadsheet app and its row action, then map the guest name, email, day and hour from the OctoTable booking into the matching columns.
- 05
Test, then publish
Run each step once and read what came back. When the row looks right, click Publish to switch the Zap on. Only bookings made after that moment go through.
The 3 OctoTable triggers
3 events start a Zap when something happens in OctoTable. Zapier checks for them at the interval your plan allows.
Reservation Cancelled
Polling triggerIn Zapier“Triggers when a reservation is canceled.”
Starts your Zap each time a booking is called off in OctoTable, carrying that reservation's details to the next step. It turns a quiet change in the book into something the team actually sees.
New Reservation
Polling triggerIn Zapier“Triggers when there's a new reservation.”
Fires on every fresh booking that lands in OctoTable, whoever made it. This is the trigger most restaurant Zaps start from, because a new reservation is the event everything else depends on.
Reservation Updated
Polling triggerIn Zapier“Triggers when a reservation is modified.”
Reacts when an existing booking is changed in OctoTable, for example a new time or a different party size. The Zap receives the booking as it stands after the change.
The 2 OctoTable actions
OctoTable gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Cancel Reservation
ActionIn Zapier“Triggers when a reservation is canceled.”
Calls off an existing OctoTable booking from another tool, using the guest's email and the day of the reservation to find it.
New Reservation
ActionIn Zapier“Creates a new reservation in the system”
Writes a fresh booking into OctoTable from whatever started the Zap: a web form, an event ticket, a private-dining request.
When the OctoTable Zap breaks
Zapier links no help article to OctoTable, and no rate limit is documented for it. What breaks is the general Zapier behaviour, applied to a reservation book.
Four general Zapier behaviours apply to a booking setup like this one. Read them before publishing, and the Zapier troubleshooting guide when something still goes wrong.
Old bookings never come through
A Zap only reacts to what happens after you switch it on. The reservations already in OctoTable stay where they are; moving them is a separate job.The Zap keeps firing itself
If a step creates or cancels a booking in OctoTable while a trigger watches those same events, the Zap sets itself off again and burns tasks fast.A bulk import gets held back
After a big import or a move from another booking tool, a sudden batch of new items can be paused by Zapier's flood protection.The same booking will not run twice
Zapier remembers what a polling trigger has already seen. A reservation that went through once will not start the Zap again on the next check.
Need help automating OctoTable with Zapier?
A person reads every message.
