Occasion Zapier integrationAutomate Occasion with Zapier.
The Occasion Zapier integration has 1 trigger, no action and no search step. That trigger, New Booking, is instant: each reservation reaches Zapier as soon as it is made, even on the free plan, and Occasion is not a premium app. Everything else happens in the apps you connect after it.
Verified Trustpilot reviews · AI, automation & growth agency
What the Occasion Zapier integration does for a booking business
Occasion is a scheduling and marketing platform for businesses that sell group experiences: classes, workshops, tours, tastings. Zapier watches it for you. The integration does one thing: every new booking in Occasion starts a Zap, and that Zap carries the booking to any other app you use.
One trigger, but plenty of results. A booking log your team can read: New Booking adds each reservation to a shared sheet, so the person preparing tomorrow's session sees the head count without logging in to Occasion. A customer list that grows on its own: the same trigger sends each buyer to your email or CRM tool, ready for the next newsletter or a review request after the event. An alert for the team on site: a message in your chat tool every time a slot fills, handy when the instructor needs to know who is coming.
Because the trigger is instant, none of this waits for a timer. That matters more than it sounds: on the free plan, a polling trigger would check only every 15 minutes, while this one reacts at once.
Now what Zapier does not do for Occasion. There is no action, so a Zap cannot create, change or cancel a booking in Occasion. There is no search step either, so a Zap cannot look up an existing customer or event. Occasion only talks; it never listens.
If you are still weighing up the tool itself, start with our Zapier review.
Zapier words, in one minute
A handful of words come back on every block. Here they are in plain English.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time that trigger happens.
- Trigger
- The event in an app that starts the Zap. For Occasion, it is a new booking; Zapier waits for it once the Zap is on.
- Action
- What the Zap does after it starts: the step that writes, sends or adds something in another app on your behalf.
- Task
- What Zapier bills. One task is one action that completed successfully, and your plan counts those each month.
- Instant vs polling
- An instant trigger is reported by the app the moment it happens. A polling trigger is checked by Zapier on a timer.
- Filter
- A step that lets the Zap go on only when the booking meets your condition, and stops it there otherwise.
- Connection
- Your Occasion account linked to Zapier once, then reused by every Zap that starts from a booking.
What an Occasion Zap really costs
Watching Occasion for bookings costs nothing. You pay for what the Zap does with each one.
- New Booking triggerNever costs a task
- Successful action1 task each
- Free plan100 tasks a month, two-step Zaps
- Premium appNo, Occasion works on the free plan
The trigger never uses a task. Each action that succeeds in the apps after it uses one, and a failed action is not counted. A Zap that logs a booking and also emails the team is two actions, so two tasks per booking. The free plan gives you 100 tasks a month and unlimited Zaps, limited to two steps each: one trigger, one action. A filter or a second action makes it multi-step and needs a paid plan. The interval grid below is for polling triggers: New Booking is instant, so it never waits for it.
Connect your Occasion account in three steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. You need an Occasion account, and access to the bookings of any business you do not own yourself.
- 02
Find Occasion
Type Occasion in the search box of the dialog, pick it from the list, then click Add connection. A new browser tab opens on the Occasion side so you can sign in.
- 03
Sign in and grant access
Log in to Occasion in that tab and allow Zapier to reach the account. The connection is then listed under Apps, and every Zap that starts from a booking picks it there.
Your first Zap: a booking log for the team
GoalEach new Occasion booking for a chosen experience lands as a row in a shared sheet the team checks before every session.
- 01
Create the Zap
Start a new Zap. Pick Occasion as the trigger app and New Booking as the event, then choose the connection you made earlier.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent bookings of the account, so you build the rest on a real reservation. No booking yet? Make a test one first.
- 03
Add a filter
From the plus icon, add Filter. Pick, among the fields the test booking brought back, the one that names the experience, then a text rule and the name you want to log.
- 04
Add the action
Pick your sheet app and the step that adds a row, then map the booking details your team needs, as they appeared in the test, into the columns.
- 05
Publish
Click Publish. With the filter, the Zap is multi-step and runs on a paid plan. On the free plan, drop the filter and log every booking instead.
The Occasion trigger
1 event starts a Zap when something happens in Occasion, and one of them is instant: the app calls Zapier straight away, whatever your plan.
New Booking
Instant triggerIn Zapier“Triggers when a new booking is created.”
Starts the Zap each time a customer reserves a spot in one of your experiences on Occasion. The booking details travel with it, so the next step can file, share or announce the reservation without anyone copying it by hand.
When an Occasion Zap breaks
Zapier lists no help article and no rate limit specific to Occasion. The trouble comes from Zapier's general rules, and with booking peaks it shows quickly.
Three cases cover most of what goes wrong. For any other symptom, the Zapier troubleshooting page walks through the usual causes.
Older bookings never arrive
A Zap only reacts to what happens after you switch it on. Reservations taken before that day are not sent; moving the backlog is a separate job.A rush of bookings is held back
When a trigger suddenly hands Zapier a huge batch, after an import or a migration, Zapier's flood protection can hold it back instead of running it.The Zap will not publish on free
A filter or a second action makes the Zap multi-step. The free plan stops at one trigger and one action, so publishing asks for a paid plan.
Need help automating Occasion with Zapier?
A person reads every message.
