Resources · Zapier integration

Omnivery Zapier integrationAutomate Omnivery with Zapier.

The Omnivery Zapier integration gives you 7 triggers, 4 actions and 0 searches. The triggers follow each message (delivered, opened, clicked, bounced, reported, unsubscribed) and the actions send, check, parse or suppress addresses. All seven triggers are instant.

See the 11 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Omnivery Zapier integration does

Omnivery is a message delivery platform built around deliverability and compliance. Connected to Zapier, it reports what happens to every email you send through it (delivery, opens, clicks, bounces, spam reports, unsubscribes) and lets other apps send email, check addresses or block them without opening Omnivery.

Three results people set up first. A sending list that cleans itself: Message Bounced (Hard) or Recipient Complained runs Suppress Email, so the address stops receiving mail from you. A CRM that knows who engaged: Message Opened and Message Clicked pass each reader to your sales tool. Sign-ups checked before the first send: a form entry goes through Validate Email, then Send Email only writes to an address that holds up.

What Zapier does not do here matters as much. There is no search, so a Zap cannot look up past messages or the state of a suppression list. No action removes an address from suppression or edits a message once sent. Each trigger listens to one sending domain, so several domains mean several Zaps, each with its own Domain typed in. And a Zap never replays what happened before it was published.

If you are weighing tools for this job, two comparisons sit on the site: n8n vs Zapier and Make vs Zapier.

Vocabulary

Zapier vocabulary, in plain words

Eight words come back throughout 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 Omnivery event that starts the Zap, such as a delivered, opened or bounced message. Once the Zap is on, Zapier waits for it.
Action
What the Zap does after it starts: the step that sends an email, checks an address or suppresses one 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 Omnivery trigger is instant.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it right there otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action or a filter makes one, and it then needs a paid plan.
Connection
Your Omnivery account linked to Zapier once, then reused by every step of every Zap that touches Omnivery.
Cost

What an Omnivery Zap really costs

Zapier bills what gets done, not what gets watched. The trigger never costs a task, and since all Omnivery triggers are instant, the polling grid below does not apply to them.

  • Trigger0 tasks
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps
  • Premium appNo

Each action that succeeds counts as one task; a failed one is not counted. On a busy domain that adds up: a Zap on Message Delivered runs once per delivered email. The free plan gives 100 tasks a month and two-step Zaps only. A second action or a filter makes the Zap multi-step, which needs a paid plan. Omnivery 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.

Connect

Connect your Omnivery 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 Omnivery in the search box of the dialog and pick it. You need an Omnivery account of your own first.

  2. 02

    Sign in to Omnivery

    Click Add connection and sign in to Omnivery in the tab that opens. Use the account that holds the sending domains your Zaps will use: a domain managed by someone else needs read or write access granted to you.

  3. 03

    Grant Zapier access

    Approve the access Zapier asks for on your Omnivery account. Every Omnivery step in every Zap then reuses this connection, so you sign in once, not once per Zap.

First Zap

Your first Omnivery Zap: act on spam complaints

GoalEvery spam complaint blocks the address and leaves a line in a shared sheet.

  1. 01

    Set the trigger

    Build a Zap with Omnivery as the starting app and Recipient Complained as the event, on your Omnivery connection. Enter the Domain to listen to, then test to pull back a recent complaint.

  2. 02

    Suppress the address

    Add Suppress Email. Pick the same Domain, map Address from the complaint the trigger delivered, then choose the Suppression type that fits your policy.

  3. 03

    Log it

    Add Google Sheets with Create Spreadsheet Row to keep a record for whoever handles compliance. Two actions make the Zap multi-step, which needs a paid plan.

  4. 04

    Test each step

    Run each step once and read what came back before moving on. If the trigger brings nothing back, check the Domain spelling first.

  5. 05

    Publish

    Click Publish to switch the Zap on. Complaints received earlier are not picked up. For guided help on builds like this one, there is the Zapier training.

Triggers

The 7 Omnivery triggers

7 events start a Zap when something happens in Omnivery, and 7 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Message Clicked

Instant trigger

In Zapier“Triggers when a link in a message is clicked on by the recipient.”

Starts the Zap when a recipient clicks a link in one of your messages. A click says more than an open, so this is the trigger for real interest.

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 SaaS team that wants each click on the pricing link of its onboarding email turned into a task for the account executive.
Watch out
the trigger listens to the one Domain you enter, so messages sent from another domain never reach this Zap.
2

Recipient Complained

Instant trigger

In Zapier“Triggers when a recipient reports message as spam.”

Fires when a recipient reports your message as spam. Of all seven events, this is the one your sending reputation cares about most.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
blocking the address with Suppress Email and warning the person in charge of compliance, before the next campaign goes out.
Watch out
complaints received before the Zap was published are never replayed, so check your existing list separately.
3

Message Delivered

Instant trigger

In Zapier“Triggers when a message is delivered to the recipient.”

Reacts each time a message reaches the recipient. It is the confirmation event, the one that proves a transactional email actually arrived.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
marking an invoice as sent in your accounting tool once Omnivery confirms delivery.
Watch out
this event fires for every delivered email, so on a busy domain each action behind it eats a task per message, and a Send Email step behind it loops.
4

Message Bounced (Hard)

Instant trigger

In Zapier“Triggers when a message delivery results in hard-bounce (temporary failure).”

A delivery that ends in a hard bounce starts this Zap. A hard bounce points to an address you probably want off your list before it hurts the rest of your sending.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
pairing it with Suppress Email so an address that hard-bounced stops receiving mail, and flagging the contact in the CRM.
Watch out
Zapier's own description of this event calls it a temporary failure, the same words as the soft bounce, so check how Omnivery classifies it before automating a deletion.
5

Message Opened

Instant trigger

In Zapier“Triggers when a message is opened by the recipient.”

Each open of one of your messages by a recipient sets this one off. It is the widest engagement signal Omnivery hands to Zapier, and the noisiest.

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 training company that adds a note in the CRM when a prospect opens the course brochure email.
Watch out
opens can come in large numbers after a big send, so put a filter early or the task count goes fast.
6

Message Bounced (Soft)

Instant trigger

In Zapier“Triggers when a message delivery results in soft-bounce (temporary failure).”

Reacts when a delivery fails temporarily, a soft bounce. The address is not necessarily dead, which is why this trigger calls for watching rather than blocking.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
logging soft bounces in a sheet so someone can spot an address that keeps failing.
Watch out
wiring it straight to Suppress Email would block addresses that might have worked on the next attempt.
7

Recipient Unsubscribed

Instant trigger

In Zapier“Triggers when a recipient unsubscribes from the message.”

Someone leaving your mailings is the event here: a recipient unsubscribes from one of your messages. It lets every other tool that writes to that person know about the choice.

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 contact's status in your newsletter tool and CRM, so no other system keeps mailing someone who opted out.
Watch out
unsubscribes recorded before the Zap went live stay where they are and need a one-off sync.
Actions

The 4 Omnivery actions

Omnivery gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Parse Email

Action

In Zapier“Parses an input string and returns a well formed array of valid and unparseable emails”

Takes a block of text holding several addresses and sorts them into valid ones and ones it could not read. The only field is Addresses, a comma-separated list.

When to use it
cleaning the attendee list pasted into a form before importing it.
Watch out
addresses separated by anything but commas will not split as expected.
2

Send Email

Action

In Zapier“Sends and Email message”

Sends an email through Omnivery from another app's event. It asks for a Sending domain, a From, a To and a Subject; From and To are written as a name followed by an address in angle brackets.

When to use it
a booking confirmation sent from your own domain.
Watch out
the From address must sit on the sending domain you entered.
3

Suppress Email

Action

In Zapier“Adds a recipient to a suppression list.”

Puts an address on a suppression list, so Omnivery stops sending to it. Three fields are required: the Domain, the Address and a Suppression type picked from the list.

When to use it
right behind Recipient Complained or Message Bounced (Hard).
Watch out
no Zapier action lifts a suppression afterwards.
4

Validate Email

Action

In Zapier“Validates an email address formating, existence and associated risks. Please note that the domain used for validation MUST have Email Validation enabled in the domain detail.”

Checks an address before you write to it: its format, whether it exists, and the risks attached to it. It needs a Domain and the Email to test.

When to use it
screening sign-ups from a form before they enter any list.
Watch out
the Domain needs Email Validation enabled in its domain detail.
When it breaks

When an Omnivery Zap breaks

Zapier links no help article to Omnivery and records no rate limit for it, so the cases below come from how Zapier works and from the rules written on the Omnivery fields.

Six cases cover what the sources document. If yours is not here, the Zapier troubleshooting page is the next stop.

  • The trigger stays silent

    Each trigger listens to the single Domain you typed. A typo, or mail sent from another domain, and nothing ever reaches the Zap.

  • Validate Email fails every time

    The domain chosen for validation needs Email Validation enabled in its domain detail in Omnivery. Without it, the step cannot run.

  • Send Email is refused

    The From address must be aligned with the Sending domain. A From on another domain, or a From not written as name plus address in angle brackets, blocks the send.

  • The Zap keeps restarting

    Send Email behind Message Delivered on the same domain: each email sent is delivered, which starts the Zap again, which sends again, and every lap costs a task.

  • A big send goes quiet

    A large campaign can produce a huge batch of delivered or opened events at once, and Zapier's flood protection may hold it back instead of running the Zap.

  • Past events never arrive

    A Zap only reacts to what happens after it is published. Bounces, complaints and unsubscribes from before stay out, and syncing them is a separate job.
Need help

Need help automating Omnivery with Zapier?

A person reads every message.

FAQ

Omnivery Zapier integration: questions

01Is the Omnivery Zapier integration free?
Yes, for two-step Zaps. Omnivery 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. Message Bounced (Hard) followed by Suppress Email fits. Add a second action, like the spreadsheet log in the example, or a filter, and the Zap becomes multi-step, which needs a paid plan. The integration has no separate price on the Zapier side; the task count of your plan is what you spend.
02How many tasks does an Omnivery Zap use?
One per action that succeeds, and nothing for the trigger. That sounds small until you pick a high-volume event: a Zap on Message Delivered or Message Opened runs once per email, so a single campaign can use a large share of a monthly allowance. An action that fails is not counted. A Zap with three actions uses three tasks per run. Zapier also notes that a few apps and actions take more than one task when they complete, so some steps can count differently.
03Do Omnivery triggers work in real time?
Yes. All seven Omnivery triggers are instant: Omnivery tells Zapier the moment a message is delivered, opened, clicked, bounced, reported or unsubscribed, and the Zap starts right away. That holds on every plan, the free one included, because the polling interval grid only applies to triggers Zapier has to check on a timer. A Zap built on an instant trigger shows a lightning bolt in the editor. The type is set by the app and cannot be changed from the editor.
04What does connecting an Omnivery account require?
An Omnivery account with at least one sending domain, and a Zapier account. On Zapier's Apps page, click + Add connection, search for Omnivery, click Add connection, sign in to Omnivery in the tab that opens and grant access. Every trigger then asks for the Domain it should listen to, so the domain has to exist in Omnivery first. If you plan to use Validate Email, enable Email Validation in that domain's detail before building the Zap.
05Why does Send Email reject the sender?
Because the From address is not aligned with the sending domain. Send Email asks for a Sending domain and a From written as a name followed by the address in angle brackets, and the address has to sit on that same domain. A From on a different domain, or a field mapped from another app that only holds a bare name, blocks the send. The To field follows the same name plus address format, and the Subject is required too.
06What if the Omnivery operation you need does not exist?
Then Zapier cannot do it for Omnivery. The integration offers eleven visible operations: seven triggers on message events and four actions (send, validate, parse, suppress). There is no search, so a Zap cannot read past messages or check a suppression list, and no action removes an address from suppression. Chaining what exists sometimes gets close, such as Parse Email then Validate Email on each address, but anything outside these eleven stays manual in Omnivery or moves to another tool.
07Zapier, Make or n8n for Omnivery?
Choose on criteria. On Zapier, Omnivery gives seven instant triggers and four actions, works on the free plan for two-step Zaps and bills one task per successful action. That suits a team that wants bounces, complaints and unsubscribes handled right away without maintaining anything. Because events like deliveries and opens arrive one per email, volume is the deciding criterion: estimate the tasks your Zaps would use, then compare with how Make and n8n count the same work and whether they list the Omnivery operations you need.
Same platform

Other docs you might need on this stack.

Browse all integrations