Omnify Zapier integrationAutomate Omnify with Zapier.
The Omnify Zapier integration gives you 14 triggers, 1 action and 0 searches. Every trigger is instant, so bookings, check-ins, renewals and paid invoices reach your other tools right away, and Create Client brings new people into Omnify from elsewhere.
Verified Trustpilot reviews · AI, automation & growth agency
What the Omnify Zapier integration actually does
Omnify is the booking and business platform studios and coaches use to sell classes, packs and memberships in one place. Linking it to Zapier, the automation service, means every booking, check-in, renewal or paid invoice in Omnify can set off work in your other tools, and contacts gathered elsewhere can land in Omnify as clients.
Three results that come straight out of the real operations.
A follow-up for every abandoned booking. Abandoned Booking hands the half-finished reservation to your email tool, so someone who dropped off at checkout hears from you instead of disappearing.
A bookkeeping sheet that fills itself. Invoice Paid, Class Pack Renewal - Invoice and Memberships Renewal - Invoice each add a line to the sheet your accountant reads, with no copy-paste at month end.
Leads from your website turned into Omnify clients. A form reply on your site goes through Create Client, and the person exists in Omnify before they book their first class.
All 14 triggers are instant. That matters more than it sounds: the waiting time tied to your Zapier plan never applies to them, even on the Free plan.
What Zapier does not do here: there is no way to look up an existing client or booking, and the only thing it can write into Omnify is a new client. Changing a booking, cancelling one or editing an invoice stays a job for Omnify itself.
If you are weighing other tools for the same job, the comparisons are at Make vs Zapier and n8n vs Zapier.
The Zapier words you need, in plain English
Eight words cover everything on this page. After this list, each one is used exactly as defined.
- Zap
- The automation you build in Zapier: one trigger that starts it, then one or more actions that run every time that event happens.
- Trigger
- The event in an app that starts the Zap, such as a new booking in Omnify. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you, like Create Client in Omnify.
- Task
- The unit Zapier bills: one action completed successfully. The monthly allowance on your plan is a count of those, nothing else.
- Polling vs instant
- Polling: Zapier checks the app on a timer. Instant: the app tells Zapier itself when the event happens. Every Omnify trigger is instant.
- Filter
- A step that lets the Zap carry on only when what arrived meets your condition, and stops it otherwise. It needs a paid plan.
- Connection
- Your account of an app, linked to Zapier once and then reused by every step that uses that app, in every Zap you build.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action, a filter or a search makes it one, and it then requires a paid plan.
What an Omnify Zap really costs
The trigger never costs a task. A booking or a check-in arriving from Omnify is free; what gets billed is each action that then succeeds, in Omnify or in another app.
- TriggerFree, never counted
- Billed per run1 task per action that succeeds
- Free plan100 tasks a month, two-step Zaps only
- Reserved for paid plansNo, Omnify works on Free
- Integration version readOmnifyCLIAPI@1.5.0, October 2026
An action that fails is not counted. Omnify is not reserved for paid plans, so it works on Free: 100 tasks a month and unlimited Zaps, limited to two steps, one trigger and one action. Adding a filter, say to keep only one type of class, makes the Zap multi-step and paid. The interval grid below applies to polling triggers only, and Omnify has none, so your plan never slows these Zaps down, whichever one you are on.
Connect Omnify to Zapier in three steps
- 01
Open the connection dialog
In your Zapier account, go to the Apps page and click + Add connection. You need an Omnify account beforehand: Zapier links to an existing one, it never creates it.
- 02
Find Omnify and confirm
Type Omnify in the search box of the dialog, pick it from the results, then click Add connection. A new tab opens on the Omnify side so you can sign in there.
- 03
Sign in and grant access
Log in to Omnify in that tab and grant Zapier access to the account. The connection then appears on your Apps page, and every Zap that uses Omnify reuses it.
Your first Zap: win back abandoned bookings
GoalWhen a booking is marked as abandoned in Omnify, send that person a short reminder email, but only for one type of class.
- 01
Pick the trigger
Start building the Zap with Omnify as the starting app and Abandoned Booking as the event, then choose the Business it should watch. That field is required.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent abandoned bookings from the connected account, so you map the next steps on a real one rather than a guess.
- 03
Add the filter
Add a filter step and set a text rule that keeps only the class type you care about. This makes it a multi-step Zap, so it needs a paid plan; drop the filter if you want to stay on Free.
- 04
Add the email action
Pick your email app as the action and map what the trigger brought back into the message. Each email that goes out costs one task.
- 05
Test, then publish
Test the email step on yourself first. When it reads right, click Publish to switch the Zap on. Bookings abandoned before that point are not picked up.
The 14 Omnify triggers on Zapier
14 events start a Zap when something happens in Omnify, and 14 of them are instant: the app calls Zapier straight away, whatever your plan.
Abandoned Booking
Instant triggerIn Zapier“Triggers when a booking is marked as Abandoned.”
Starts your Zap when a reservation in Omnify gets the Abandoned status, meaning someone began booking and never finished. You get the unfinished booking to act on elsewhere.
Booking Detail
Instant triggerIn Zapier“Triggers when a new booking is made; forwards all the booking details in the response.”
Fires on each new booking, like New Booking, but its description promises the full booking details in what it sends. Pick it when the next step needs everything about the reservation.
Booking Update
Instant triggerIn Zapier“Triggers when a booking object is updated; forwards all the booking details in the response.”
Reacts whenever an existing reservation changes in Omnify, and passes on the full booking as it stands after the change. It is the one to watch for edits rather than new arrivals.
Checkins
Instant triggerIn Zapier“Triggers when a new check-in happens in the business.”
Goes off each time someone checks in at your business in Omnify. It turns physical attendance into an event your other tools can count or respond to.
Class Pack Renewal - Booking
Instant triggerIn Zapier“Triggers on renewal of class pack booking.”
Signals that a client has renewed a class pack, on the booking side of the renewal. Use it to celebrate or track loyalty rather than money.
Class Pack Renewal - Invoice
Instant triggerIn Zapier“Triggers when class pack renewal invoice generated in the business.”
Kicks in when Omnify generates the invoice for a class pack renewal. This is the money side of the renewal, the one your bookkeeping cares about.
Memberships Renewal - Booking
Instant triggerIn Zapier“Triggers on renewal of membership booking.”
Tells you that a membership has renewed, on the booking side. It is how a recurring member shows up in your other tools without anyone checking Omnify.
Memberships Renewal - Invoice
Instant triggerIn Zapier“Triggers when membership renewal invoice is generated in the business.”
Runs when Omnify issues the invoice for a membership renewal. Recurring revenue becomes visible outside Omnify, line by line.
New Booking
Instant triggerIn Zapier“Triggers when a new booking is made.”
The plain version: each fresh reservation made in Omnify starts the Zap. It suits most simple flows where you only need to know a booking happened.
New Client
Instant triggerIn Zapier“Triggers when a new client is added to the business.”
Fires when a client is added to your Omnify business, whether they booked online or your team created them. It is the entry point for onboarding flows.
New Lead
Instant triggerIn Zapier“Triggers when a new client is added to the business.”
Listed by Zapier under the name New Lead, yet its official description is word for word the one of New Client: a client added to the business. The source does not say what separates the two.
New Family Member
Instant triggerIn Zapier“Triggers when a new family member is added to the business.”
Triggers when someone is added as a family member in your business. Handy for kids' classes and household memberships, where one account books for several people.
Invoice Paid
Instant triggerIn Zapier“Triggers when paid invoice is generated in the business.”
Goes off when a paid invoice is generated in your business. This is money actually received, not money owed, which makes it the cleanest signal for bookkeeping.
Payment Reminder
Instant triggerIn Zapier“Triggers within 3 hours from when the booking is made.”
Omnify sends this one on its own schedule after a booking is made, which makes it a ready-made hook for following up on payment shortly after a reservation.
The Omnify action on Zapier
Omnify gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create Client
ActionIn Zapier“Adds new customer to your Omnify's business.”
Adds a new client to your Omnify business from another app, so people who reach you through a form, a quiz or an event page are ready to book.
When an Omnify Zap breaks
Zapier attaches no help article and no rate limit to Omnify, so the cases below are the ones every Zap shares, applied to a booking business. For deeper diagnosis there is Zapier troubleshooting.
The trigger side is solid because every Omnify trigger is instant. Problems come from history, from loops and from big batches.
No catching up on old bookings
A Zap only reacts to what happens after you switch it on. Last month's bookings and invoices stay where they are; moving that backlog is a separate job.New Client plus Create Client loops
A Zap that starts on New Client and writes Create Client into the same business sets itself off again and again, burning through your tasks fast.Bulk imports can be held back
Import a big client list or migrate from another tool, and the sudden batch can be held back by Zapier's flood protection instead of running every Zap.The Business field left on the wrong site
Every trigger watches the Business you chose. A studio with several locations that picks the wrong one gets a Zap that runs fine and never fires.
Need help automating Omnify with Zapier?
A person reads every message.



