Resources · Zapier integration

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

Overview

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.

Vocabulary

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.
Cost

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

Connect your Omnito account in three steps

  1. 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.

  2. 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.

  3. 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.

First Zap

Your first Omnito Zap: book every new contact

GoalEach new contact in Omnito gets a meeting on a slot that is actually free.

  1. 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.

  2. 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.

  3. 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.

  4. 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:mm with no offset added.

  5. 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.

Triggers

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.

1

New Contact Created

Instant trigger

In 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.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a sales team that wants each new Omnito contact copied into its CRM without anyone retyping it.
Watch out
contacts that existed before you published the Zap are never picked up, so an old address book stays where it is.
2

Contact Updated

Instant trigger

In 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.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
keeping a second tool in step with Omnito, so a correction made on one side reaches the other without anyone cleaning up by hand.
Watch out
pairing it with the Update Contact action on the same account sets off a loop, since the Zap's own edit counts as an update, and every lap costs a task.
3

New Conversation Created

Instant trigger

In 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.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a support lead who wants each new conversation announced in the team chat, so nobody has to keep the Omnito inbox open all day.
Watch out
the Create Conversation action creates conversations too, so a Zap that uses both on the same account starts itself again.
4

Conversation Resolved

Instant trigger

In 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.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
sending a short satisfaction survey after each resolved case, or logging the closed exchange in a shared spreadsheet your manager reads.
Watch out
resolutions that happened before the Zap was published are not replayed, so any report built on it starts on the day you switch it on.
5

Meeting Canceled

Instant trigger

In 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.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
warning the account manager that a demo is off, or moving the deal back a stage in the CRM before the next pipeline review.
Watch out
meetings your own Zaps cancel with the Cancel Meeting action start this trigger as well, so keep the two in separate Zaps.
6

New Meeting Scheduled

Instant trigger

In 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.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
creating a deal in the CRM for every booked call, or posting the booking to the channel where the sales team works.
Watch out
meetings booked by a Zap through Create New Meeting count as new bookings too, which can send the same meeting around twice.
7

Meeting Rescheduled

Instant trigger

In 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.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
updating the follow-up date in your CRM, or telling the colleague who was preparing the call that it moved.
Watch out
a Zap that moves meetings with the Reschedule Meeting action sets this trigger off again on the same account.
Actions

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.

1

Add Attendee to Meeting

Action

In 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.

When to use it
adding the account manager to every demo booked by a large prospect.
Watch out
a missing comma merges two addresses into one invalid entry.
2

Cancel Meeting

Action

In 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.

When to use it
a deal marked as lost in the CRM should free the follow-up call booked for it.
3

Create Contact

Action

In 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.

When to use it
a landing page form that should feed Omnito directly, instead of an import done by hand.
4

Create Conversation

Action

In 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.

When to use it
starting a written exchange with a contact right after a booking, so the thread already exists when the meeting starts.
5

Create New Meeting

Action

In 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.

When to use it
booking a discovery call for each qualified lead.
Watch out
Start Time follows YYYY-MM-DD HH:mm with no offset, and Find Available Times should run first.
6

Reschedule Meeting

Action

In 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.

When to use it
a shift planning tool that changes a slot and should move the matching Omnito meeting.
Watch out
same date format as booking, and the Time Zone goes in Region/City form, like Asia/Tokyo.
7

Update Contact

Action

In 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.

When to use it
bringing a correction made in your CRM back into Omnito.
Watch out
inside a Zap started by Contact Updated, it loops on itself.
Searches

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.

1

Find Available Times

Search

In 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.

When to use it
just before Create New Meeting or Reschedule Meeting, as Omnito itself recommends.
2

Find Contact

Search

In 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.

When to use it
in front of Update Contact, when the trigger only carries an email address.
Watch out
with no match and the default setting, the Zap stops here.
3

Find Scheduled Meeting

Search

In 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.

When to use it
picking the right Event before Add Attendee to Meeting, Reschedule Meeting or Cancel Meeting, when the trigger came from another app.

The three settings every search exposes

  1. 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.
  2. 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.
  3. 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 it breaks

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

Need help automating Omnito with Zapier?

A person reads every message.

FAQ

Omnito Zapier integration: frequent questions

01Is the Omnito Zapier integration free?
Yes, as long as the Zap stays at two steps. Omnito is not a premium app, so it works on Zapier's free plan, which gives 100 tasks a month and Zaps made of one trigger and one action. New Meeting Scheduled followed by Create Conversation fits. The moment you add a search such as Find Available Times, a filter or a second action, the Zap becomes multi-step and needs a paid plan. The integration itself has no separate price on the Zapier side, only your plan's task count matters.
02How many tasks does an Omnito Zap use?
One per action that succeeds, and nothing for the trigger. A Zap that starts on Meeting Canceled and then runs Create Conversation costs one task per cancellation. A Zap with three actions costs three tasks each time it runs to the end. An action that fails is not counted against your plan. Zapier notes that a few apps and actions take more than one task when they complete, so the count can differ for some steps. The trigger, and Zapier waiting for the next Omnito event, never consume anything.
03Do Omnito triggers work in real time?
Yes. All seven Omnito triggers are instant: Omnito tells Zapier the moment the booking, cancellation, contact or conversation event happens, and the Zap starts right away. That holds on every plan, including the free one, because the polling grid only applies to triggers Zapier has to check on a timer. In the editor, a Zap built on an instant trigger shows a lightning bolt. The type cannot be changed from the editor, so nothing needs adjusting on your side for this to work.
04What does connecting an Omnito account require?
An Omnito account and a Zapier account, nothing more. On the Apps page of Zapier, click + Add connection, search for Omnito, click Add connection, sign in to Omnito in the tab that opens and grant access. If the Zap must touch meetings, contacts or inboxes that belong to a colleague, the connected account needs read or write access to them. Several actions also expect things to exist on the Omnito side already, such as a Meeting Type for bookings or an Inbox for conversations.
05Why does Create New Meeting reject a start time?
Because the format is strict. Start Time must be written YYYY-MM-DD HH:mm, with no time zone offset added to it. The time zone goes in its own Time Zone field, as a Region/City value like Asia/Tokyo. Reschedule Meeting follows the same two rules. Omnito also recommends running Find Available Times first, so the slot you send is one that can actually be booked. When another app hands over its date in a different shape, that conversion has to happen before this step, otherwise the booking fails.
06What if the Omnito operation you need is not listed?
Start by checking whether two existing steps cover it together. Many gaps close that way: Find Contact plus Update Contact edits a contact you only know by email, Find Scheduled Meeting plus Cancel Meeting cancels a meeting the trigger did not carry. If the operation really does not exist among the 17 on offer, such as deleting a contact, Zapier will not do it for Omnito, and the job either stays manual or moves to another tool. Only the operations the editor offers count: nothing outside that list of 17 can be added to a Zap.
07Zapier, Make or n8n for Omnito?
Decide on criteria rather than reputation. On Zapier, Omnito brings seven instant triggers, seven actions and three searches, works on the free plan for two-step Zaps, and bills one task per successful action. That suits a team that wants a booking or a cancellation to reach another tool without maintaining anything. If your scenarios need many steps, searches and filters on high volumes, compare the task count those Zaps would use with how Make and n8n count the same work, and check that the Omnito operations you rely on exist there too.