Omnito Zapier integrationAutomate Omnito with Zapier.
The Omnito Zapier integration gives you 7 triggers, 7 actions and 3 searches to wire your scheduling into the rest of your tools. All seven triggers are instant, Omnito is not a premium app, and the free plan already runs a two-step Zap.
Verified Trustpilot reviews · AI, automation & growth agency
What the Omnito Zapier integration actually does
Omnito is a scheduling platform: teams use it to take bookings, manage availability and keep track of contacts and conversations. The Zapier integration lets a booking, a cancellation or a new contact in Omnito start an automation, and lets other apps book, move, cancel or update things in Omnito without anyone opening it.
Three results people usually build first. A CRM that never misses a booking: New Meeting Scheduled pushes each new meeting to the tool your sales team lives in. A calendar that books itself: a lead arrives elsewhere, Find Available Times looks for a free slot and Create New Meeting books it. A support desk that closes properly: Conversation Resolved hands the finished exchange to whatever logs or follows up on it.
What Zapier does not do here matters just as much. There is no action to delete a contact, and no find-or-create version of the three searches, so a missing contact is not created on the fly. A Zap also only reacts to what happens after you switch it on: last month's meetings stay where they are. And because every Omnito trigger is instant, the polling interval of your plan never slows these Zaps down.
If you are weighing other tools for the same job, two comparisons sit on the site: n8n vs Zapier and Make vs Zapier.
Zapier vocabulary, in plain words
Eight words come back on every line of this page. Here is what each one means before you meet it in the editor.
- Zap
- The automation you build in Zapier: one trigger, then one or more actions that run every time that trigger event happens.
- Trigger
- The Omnito event that starts the Zap, such as a new contact or a canceled meeting. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does after it starts: the step that creates, updates or sends something in Omnito or in another app for you.
- Task
- The unit Zapier bills. One task is one action your Zap completes successfully, and the count on your plan is a count of those.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself. Every Omnito trigger is instant.
- Filter
- A step that lets the Zap go on only when what arrived meets a condition you set, and stops it right there otherwise.
- Search step
- A step that looks up something that already exists in an app, a contact or a free slot, so the next steps can use what it found.
- Connection
- Your Omnito account linked to Zapier once, then reused by every step of every Zap that touches Omnito.
What an Omnito Zap really costs
Zapier bills what gets done, not what gets watched. The trigger never costs a task, and since all Omnito triggers are instant, the polling grid below does not apply to them.
- Trigger0 tasks, whatever happens
- Each successful action1 task
- Free plan100 tasks a month, two-step Zaps
- Premium appNo, free plan included
Each action that succeeds counts as one task; an action that fails is not counted. The free plan gives 100 tasks a month and builds two-step Zaps only: one trigger, one action. Add a second action, a filter or a search step and the Zap turns multi-step, which needs a paid plan. Omnito is not a premium app, so it works from the free plan. A few apps and actions take more than one task when they complete, so read one task per action as the usual case, not a promise.
Connect your Omnito account in three steps
- 01
Open Apps and add a connection
In your Zapier account, open the Apps page and click + Add connection. Type Omnito in the search box of the dialog and pick it. The one prerequisite is an Omnito account of your own.
- 02
Sign in to Omnito
Click Add connection, then sign in to Omnito in the tab that opens. Use the account that can see the meetings, contacts and inboxes the Zap should touch: anything you do not own needs read or write access granted to you.
- 03
Grant Zapier access
Approve the access Zapier asks for on your Omnito account. From then on, every Omnito step in every Zap reuses this connection, so you sign in once rather than once per Zap.
Your first Omnito Zap: book every new contact
GoalEach new contact in Omnito gets a meeting on a slot that is actually free.
- 01
Start with the trigger
Build a Zap with Omnito as the starting app and New Contact Created as the event, on your Omnito connection. The test brings back the three most recent contacts, so you map from a real one.
- 02
Look for a free slot
Add Find Available Times next. It needs the Meeting Type to book and a Time Zone written as Region/City, like
America/New_York. This search makes the Zap multi-step, so it needs a paid plan. - 03
Book the meeting
Add Create New Meeting. Map the Start Time from a slot the search found, repeat the Meeting Type and Time Zone, then fill Invitee Full Name and Invitee Email from the contact the trigger delivered.
- 04
Test each step
Run every step once and read what came back before moving on. If booking fails, look at the Start Time first: it must follow
YYYY-MM-DD HH:mmwith no offset added. - 05
Publish
Click Publish to switch the Zap on. Contacts created before that moment are left alone. For a guided run through this kind of build, see Zapier training.
The 7 Omnito triggers
7 events start a Zap when something happens in Omnito, and 7 of them are instant: the app calls Zapier straight away, whatever your plan.
New Contact Created
Instant triggerIn Zapier“Triggers when a contact is created in SUMO1.”
Every contact that lands in your Omnito account becomes the starting point of a Zap, so the follow-up you used to do by hand runs on its own, from the CRM entry to the welcome message.
Contact Updated
Instant triggerIn Zapier“Triggers when a contact is updated in SUMO1.”
This one watches edits rather than arrivals: when someone changes a contact record in Omnito, the Zap receives the updated contact and carries it to the next step.
New Conversation Created
Instant triggerIn Zapier“Triggers when a conversation is created in SUMO1.”
A conversation opened in Omnito starts the Zap, which is how you get new exchanges out of the inbox they arrived in and in front of the people who should answer them.
Conversation Resolved
Instant triggerIn Zapier“Triggers when a conversation is resolved in SUMO1.”
Where the previous trigger opens the file, this one closes it: the Zap starts when a conversation is marked as resolved in Omnito, not when it begins.
Meeting Canceled
Instant triggerIn Zapier“Triggers when a meeting is canceled in SUMO1.”
A cancellation in Omnito becomes something you can act on: the Zap starts with the canceled meeting in hand and lets the next steps clean up after it.
New Meeting Scheduled
Instant triggerIn Zapier“Triggers when a meeting is booked in SUMO1.”
The obvious starting point: a meeting gets booked in Omnito and the Zap starts with that booking, ready to spread it to every tool that needs to know.
Meeting Rescheduled
Instant triggerIn Zapier“Triggers when a meeting is rescheduled in SUMO1.”
Moved meetings are the ones that slip through the cracks, and this trigger catches them: the Zap starts when an existing Omnito meeting gets a new time.
The 7 Omnito actions
Omnito gives you 7 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Add Attendee to Meeting
ActionIn Zapier“Add attendee to a meeting in SUMO1.”
Brings more people into a meeting that already exists. It needs the Event and the Attendees Emails, written as a comma-separated list.
Cancel Meeting
ActionIn Zapier“Cancel a meeting in SUMO1.”
Cancels a meeting in Omnito. Two fields are required: the Event to cancel and a Cancel Reason, so decide up front what that reason will say.
Create Contact
ActionIn Zapier“Create a contact in SUMO1.”
Adds a contact to your Omnito account from whatever the trigger brought, so a lead caught in a form or another tool is ready to be booked.
Create Conversation
ActionIn Zapier“Create a conversation in SUMO1.”
Opens a conversation in one of your Omnito inboxes, with the message you set. Both the Inbox and the Message are required.
Create New Meeting
ActionIn Zapier“Schedule a meeting in SUMO1.”
Books a meeting in Omnito for someone, without that person going through your booking page. It asks for a Meeting Type, a Start Time, a Time Zone, the invitee's full name and email.
YYYY-MM-DD HH:mm with no offset, and Find Available Times should run first.Reschedule Meeting
ActionIn Zapier“Reschedule a meeting in SUMO1.”
Moves an existing meeting to a new time. It asks for the Event, the new Start Time and the Time Zone.
Asia/Tokyo.Update Contact
ActionIn Zapier“Update a contact in SUMO1.”
Changes an existing Omnito contact. You must tell it which Contact to edit, which is why Find Contact usually sits just before it.
The 3 Omnito searches
3 search steps look for data that already exists in Omnito, so a later step can use it.
Searches sit at the bottom of the action event list, under their own SEARCH heading. Each one makes the Zap multi-step, so it needs a paid plan. Three settings decide what happens when a search does not find exactly one result.
Find Available Times
SearchIn Zapier“Finds available time slots in SUMO1.”
Looks for open slots in your Omnito availability, for a given Meeting Type and Time Zone, so a later step can book one that is really free.
Find Contact
SearchIn Zapier“Finds a Contact in SUMO1.”
Finds an existing contact from its Contact Email, which is the only required field, and hands it to the steps that follow.
Find Scheduled Meeting
SearchIn Zapier“Finds a Scheduled Meeting in SUMO1.”
Retrieves a meeting already on the books, with an Is Canceled option to tell canceled meetings from live ones.
The three settings every search exposes
- Successful if no search results are found?Left on its default, an empty search stops the Zap and skips the steps that relied on it. Switched on, the Zap goes on empty-handed.
- Create X if it doesn't exist yet?This box turns a search into find-or-create. Omnito offers no such variant, so a missing contact is not created by the search.
- If multiple search results are found?Three ways out: keep the first match (the default), stop the Zap, or hand every match to the next steps at once.
When an Omnito Zap breaks
Zapier links no help article to Omnito and lists no rate limit for it, so the failures below come from how Zapier works and from the format rules written on the Omnito fields.
Six cases cover what Zapier and the Omnito fields document. If a case is not on the list, the Zapier troubleshooting page is the next stop.
The Zap ignores past meetings
A Zap only reacts to what happens after it is published. Bookings, contacts and conversations from before stay out, and moving that backlog is a separate job.The Zap keeps starting itself
Update Contact inside a Zap started by Contact Updated, or Create New Meeting under New Meeting Scheduled: the Zap writes where it watches and burns tasks on every lap.A bulk import goes quiet
Importing many contacts at once can make a trigger return a huge batch, and Zapier's flood protection may hold it back instead of running the Zap for each one.Start Time is rejected
Create New Meeting and Reschedule Meeting expect YYYY-MM-DD HH:mm, with no offset glued to the time. The offset belongs in the separate Time Zone field.Time Zone is not recognised
The Time Zone field wants a Region/City value such as America/New_York. An abbreviation or a bare offset is not what it asks for.Cancel Meeting stops on an empty reason
Cancel Reason is required. If the trigger delivers nothing to map into it, type a fixed reason in the field so the step never runs with a blank.
Need help automating Omnito with Zapier?
A person reads every message.



