omni.us Zapier integrationAutomate omni.us with Zapier.
The omni.us Zapier integration gives you 3 triggers, 1 action and 0 searches. The triggers follow your email campaigns (opens, replies, sends) and the action adds a lead to a campaign. All three triggers are polling, so your plan decides how fast they react.
Verified Trustpilot reviews · AI, automation & growth agency
What the omni.us Zapier integration does
omni.us is an email marketing automation tool that organises your campaign leads. Connected to Zapier, it reports what happens to those leads (an email sent, opened or answered) to your other tools, and lets other apps feed new leads into a campaign without an import done by hand.
Three results people build first. A sales team that hears about replies: Lead Replies hands every answering lead to the CRM or the chat where a rep picks it up. A warm list that builds itself: Lead Opens spots the leads who opened, and Add Lead drops them into a second, more direct campaign. A campaign fed by your forms: a sign-up in another app becomes a lead in the campaign of your choice through Add Lead.
What Zapier does not do here matters too. None of the three triggers is instant: Zapier checks omni.us on a timer, every 15 minutes on the free plan, so a reply never reaches your CRM the second it lands. There is no search, so a Zap cannot look up an existing lead, and the only action adds leads: nothing edits, pauses or removes them. A Zap also ignores everything that happened before it was published.
If you are comparing tools for this kind of work, two comparisons sit on the site: n8n vs Zapier and Make vs Zapier.
Zapier vocabulary, in plain words
Eight words keep coming back below. 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 omni.us event that starts the Zap, such as a lead opening or answering a campaign email. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does once started: here, Add Lead, the step that puts a new lead into one of your omni.us campaigns.
- 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 trigger
- A trigger Zapier checks on a timer, asking the app for new items and keeping only what it has not seen. All omni.us triggers work this way.
- Instant trigger
- A trigger the app reports itself, with no wait for the next check. omni.us has none on Zapier, which is why its timing depends on your plan.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it there otherwise.
- Connection
- Your omni.us account linked to Zapier once, then reused by every step of every Zap that touches omni.us.
What an omni.us Zap costs
Zapier bills what gets done, not what gets watched. Checking omni.us for new opens, replies or sends costs nothing, however often Zapier looks, and the trigger itself never costs a task.
- Trigger checks0 tasks
- Each lead added1 task
- Free plan100 tasks a month, two-step Zaps
- Premium appNo
Each action that succeeds counts as one task, and a failed one is not counted. The free plan gives 100 tasks a month, checks polling triggers every 15 minutes and builds two-step Zaps only. A filter or a second action makes the Zap multi-step, which needs a paid plan. omni.us is not a premium app, so it opens from the free plan. On paid plans the check interval can be changed, and a check can be run by hand.
Connect your omni.us account in three steps
- 01
Open Apps and add a connection
In your Zapier account, open the Apps page and click + Add connection. Type omni.us in the search box of the dialog and pick it. You need an omni.us account of your own first.
- 02
Sign in to omni.us
Click Add connection and sign in to omni.us in the tab that opens. Use the account that holds the campaigns the Zap will watch or feed: campaigns owned by a colleague need read or write access granted to you.
- 03
Grant Zapier access
Approve the access Zapier asks for on your omni.us account. Every omni.us step in every Zap then reuses this connection, so you sign in once, not once per Zap.
Your first omni.us Zap: move openers to a follow-up campaign
GoalLeads who open your first campaign land in a second, more direct one.
- 01
Set the trigger
Build a Zap with omni.us as the starting app and Lead Opens as the event, on your omni.us connection. The test brings back the three most recent opens, so you map from a real lead.
- 02
Keep the right leads
Add a Filter step and fill its three boxes: the value to look at, the rule, the value to compare with. Pick a text rule for text. The filter makes the Zap multi-step, which needs a paid plan.
- 03
Add the lead
Add Add Lead. Choose the follow-up campaign in Campaigns, then map First Name and Email Address from the lead the trigger delivered. Both are required.
- 04
Test each step
Run each step once and read what came back before going further. If Add Lead stops, check first that the trigger sample carried a first name.
- 05
Publish
Click Publish to switch the Zap on. Opens recorded before that moment are not picked up. For guided help on builds like this one, there is the Zapier training.
The 3 omni.us triggers
3 events start a Zap when something happens in omni.us. Zapier checks for them at the interval your plan allows.
Lead Opens
Polling triggerIn Zapier“Triggers when a customer opens an OmniOutreach email”
Starts the Zap with a lead who opened one of your campaign emails. It is the earliest sign of interest omni.us passes to Zapier, well before anyone answers.
Lead Replies
Polling triggerIn Zapier“Triggers when new campaign got replied from customer”
Fires on the event that matters most in a cold campaign: a lead who answered. The Zap starts with that lead and can hand it to whoever should take over the conversation.
Lead Sent
Polling triggerIn Zapier“Triggers when a new campaign sequence is sent to a lead”
Reacts to the sending side: a campaign sequence went out to a lead, and the Zap starts with that lead in hand. Useful to keep another tool aware of who has been contacted.
The omni.us action
omni.us gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Add Lead
ActionIn Zapier“Create a lead to your selected campaign”
Creates a lead inside the omni.us campaign you select, so it enters that campaign's sequence without a manual import. Three fields are required: the campaign in Campaigns, a First Name and an Email Address.
When an omni.us Zap breaks
Zapier links no help article to omni.us and records no rate limit for it, so these cases come from how Zapier handles polling triggers and from the required fields of Add Lead.
Six cases cover what the sources document. If yours is not here, the Zapier troubleshooting page is the next stop.
The Zap seems late
All three triggers are polling. On the free plan Zapier checks every 15 minutes, so an open or a reply can wait until the next check. Paid plans check more often.Past opens never show up
A Zap only reacts to what happens after it is published. Opens, replies and sends from before stay out, and moving that history elsewhere is a separate job.A lead does not start the Zap twice
Zapier remembers what it has already seen on a polling trigger, so the same item never starts the Zap a second time. That is by design, not a fault.The Zap feeds itself
Lead Sent plus Add Lead into the same campaign: if the added lead then receives the sequence, that send can start the Zap again, and burns tasks on every lap.A big send goes quiet
When a campaign goes out to many leads at once, the trigger can return a huge batch, and Zapier's flood protection may hold it back instead of running the Zap.Add Lead refuses to run
Campaigns, First Name and Email Address are all required. A trigger from another app that lacks one of them stops the step, so check the sample before publishing.
Need help automating omni.us with Zapier?
A person reads every message.
