OneCal Zapier integrationAutomate OneCal with Zapier.
The OneCal Zapier integration has 8 triggers, 0 actions and 0 searches: it reports on your bookings and lets other apps do the follow-up. Seven triggers are instant, the eighth watches a single booking, and the app runs on the free plan.
Verified Trustpilot reviews · AI, automation & growth agency
What the OneCal Zapier integration is for
OneCal helps people who juggle several calendars handle scheduling and availability in one place. The integration links your OneCal account to Zapier so that every step in a booking's life (requested, confirmed, declined, moved, cancelled) can start work in another tool. It only listens: nothing on Zapier writes into OneCal.
Three results worth building. A team that knows who is coming: Booking Confirmed passes each new meeting to a chat or email step, so the people involved hear about it outside their calendar. A sales log that stays honest: Booking Cancelled and Booking Declined feed a spreadsheet or CRM, so lost meetings are counted, not forgotten. Follow-up that tracks the real date: Booking Reschedule Confirmed tells your other tools the meeting moved, before anyone shows up on the old day.
The detail that matters most: seven of the eight triggers are instant, so OneCal itself warns Zapier and the Zap runs straight away, even on the free plan. The exception is Get Booking by ID, which Zapier checks on a timer set by your plan.
What it does not do. There is no action and no search, so a Zap cannot create, move or cancel a OneCal booking, nor look one up mid-Zap. OneCal is always the starting point, never the destination.
Comparing tools for the same job? See Make vs Zapier and n8n vs Zapier.
Zapier words in one minute
Seven words are enough to follow this page. Here they are, in plain English, applied to OneCal.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time that event happens.
- Trigger
- The OneCal event that starts the Zap, such as a booking being confirmed. 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. With OneCal, actions live in other apps.
- Task
- The unit Zapier bills: one action that completes successfully. Your plan caps how many you get each month.
- Polling vs instant
- Polling: Zapier asks the app for news on a timer. Instant: the app reports the event itself. OneCal has 7 instant triggers and 1 polling.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
- Connection
- Your OneCal account linked to Zapier once, then reused by every OneCal trigger in every Zap you build.
What it really costs
On Zapier you pay in tasks, and only completed actions count. Since OneCal only provides triggers, OneCal itself never costs you a task.
- OneCal trigger0 tasks
- Each action that succeeds1 task
- Action that fails0 tasks
- Free plan100 tasks a month, 2 steps per Zap
What you pay for is the step in the other app: one task each time it succeeds, nothing when it fails. The free plan gives 100 tasks a month and unlimited Zaps, and OneCal is not a premium app. Its limit: two steps per Zap, one trigger and one action. Add a filter (say, to keep only some bookings) or a second action and the Zap turns multi-step, which needs a paid plan. The grid below only matters for Get Booking by ID, the one polling trigger.
Connect your OneCal account
- 01
Open Apps and add a connection
In your Zapier account, open the Apps page and click + Add connection. In the dialog that appears, type OneCal in the search box and pick the app from the results.
- 02
Sign in to OneCal
Click Add connection, then sign in to OneCal in the tab that opens. You need an existing OneCal account: Zapier links an account, it does not create one for you.
- 03
Grant access
Grant Zapier access to the account. The connection is saved and every OneCal trigger reuses it. If a Zap must watch bookings you do not own yourself, your account needs read access to them.
Your first Zap: share confirmed bookings
GoalEvery booking confirmed in OneCal sends an email to the team, but only for the bookings that match your condition.
- 01
Pick the trigger
Start a new Zap, choose OneCal as the app that starts it and Booking Confirmed as the event, then select the connection you just added.
- 02
Test on real bookings
Run the trigger test. Zapier brings back the three most recent items from your account, so you map the next steps on a real booking, not an invented one.
- 03
Add the filter
Click the plus icon, add a Filter and fill its three boxes: the booking value to look at, the rule, and what to compare it with. Use a text rule on text, a number rule on numbers.
- 04
Add the email step
Add the email app as the action and map the booking details the test returned into the message, so whoever reads it sees which meeting was confirmed.
- 05
Test, then publish
Test each step once and read what came back, then click Publish. The filter makes it a multi-step Zap, which runs on a paid plan only.
OneCal triggers
8 events start a Zap when something happens in OneCal, and 7 of them are instant: the app calls Zapier straight away, whatever your plan.
Get Booking by ID
Polling triggerIn Zapier“Triggers when a specific booking is changed.”
Unlike the seven others, this trigger keeps an eye on one booking only, the one whose ID you give it, and starts the Zap when that booking changes.
Booking Cancelled
Instant triggerIn Zapier“Triggers when a booking is cancelled.”
When a booking is cancelled, OneCal hands it to the Zap, so the empty slot and the lost meeting can be dealt with somewhere other than your calendar.
Booking Changed
Instant triggerIn Zapier“Triggers when a booking is changed.”
This one is the catch-all for edits: any change to a booking starts the Zap and carries the updated booking along.
Booking Confirmed
Instant triggerIn Zapier“Triggers when a new booking is confirmed.”
A new booking is confirmed and the Zap starts with it. This is the moment the meeting is real, which makes it the usual starting point for welcome emails and team alerts.
Booking Declined
Instant triggerIn Zapier“Triggers when a booking is declined.”
Fires on the no: a booking gets declined and the Zap receives it, so the person who asked does not fall through the cracks.
Booking Requested
Instant triggerIn Zapier“Triggers when a new booking is requested.”
Someone asks for a booking and the Zap starts right there, before anything is confirmed. It is the earliest point in a booking's life you can hook into.
Booking Reschedule Confirmed
Instant triggerIn Zapier“Triggers when a booking reschedule is confirmed.”
The new date is settled: a reschedule gets confirmed and the Zap passes the moved booking on to your other tools.
Booking Reschedule Requested
Instant triggerIn Zapier“Triggers when a booking reschedule is requested.”
Somebody asks to move an existing booking, and that request alone starts the Zap, before the new time is agreed.
When it breaks
Zapier has no help article tied to OneCal, and no limit specific to the app is documented. What can go wrong is what goes wrong on any Zap.
Four cases to know before you publish. For the rest, the Zapier troubleshooting page is the next stop.
Past bookings are never picked up
A Zap only reacts to what happens after you switch it on. Bookings confirmed or cancelled before that stay out; moving them elsewhere is a separate job.Loops: one risk you avoid here
A Zap that writes where its own trigger watches sets itself off again and again. No step writes into OneCal, so a OneCal trigger cannot loop on itself.Bulk changes held back
A sudden wave of bookings, after a migration or a mass import, can be held back by Zapier's flood protection instead of running through.The same change seen once
On Get Booking by ID, Zapier remembers what it has already seen, so the same item does not start the Zap twice, even across several checks.
Need help automating OneCal with Zapier?
A person reads every message.



