Resources · Make integration

Omnivery Make integrationAutomate Omnivery with Make.

Can Make handle your Omnivery email work without a line of code? The Omnivery Make integration gives you 6 modules: 1 scheduled trigger and 5 actions. This guide is for anyone new to Make who sends email through Omnivery, and it walks you from connection to a first working scenario.

Try the Omnivery integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Omnivery Make integration do?

The Omnivery Make integration links your Omnivery account to Make, a visual tool where you build a scenario: a chain of modules that runs on a schedule or when an app calls Make. Each module is one brick of that chain. Here, the bricks let you watch Omnivery events, check or suppress an email address, read an email and send a message.

Keep your sending list clean. A contact arrives from a form in another app. Validate Email checks the address before anything goes out, and Send a Message comes after it. The idea is simple: a doubtful address never gets a message.

React to what happens after a send. Watch for Events is the one trigger of the app. Make checks Omnivery on the scenario's schedule, and each new event becomes a bundle, one item that flows to the next module. From there you can route it wherever your team works, or, if the event carries an address, pass it to Suppress Email so it is left out of future sends.

Turn incoming mail into data. Parse Email is the module to try when an email carries information you want to reuse further down the scenario.

Know the limits before you start. Make's own documentation for Omnivery is marked as limited: it lists the module names without describing their fields, so check each module in the editor before you rely on it. Make an API Call covers anything the five named modules leave out. If you are still weighing tools, the n8n vs Make comparison lays out the choice, and the Make pricing page explains how operations are counted.

Connect

How do you connect Omnivery to Make?

  1. 01

    Add an Omnivery module

    In your scenario, click the + and search for Omnivery, then pick any of its modules. Make asks for a connection, which is your Omnivery account linked to Make once and reused by every Omnivery module. Click Create a connection to start.

  2. 02

    Name the connection

    Giving the connection a name is optional, but it helps later. If you run a test account and a live account, a clear name tells you at a glance which one a module is using when you open the scenario again.

  3. 03

    Authorize and save

    Depending on what Omnivery offers, either approve Make on the Omnivery page that opens or paste the key Omnivery gives you. Then click Save. The connection now appears in the module, ready for the next field.

First scenario

Build your first scenario with Omnivery

GoalWhen a new contact comes in from another app, Make checks the address with Omnivery, then sends the message through Omnivery.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Start with the app where your contacts come from, such as a form tool or a spreadsheet.

  2. 02

    Add Validate Email

    Click the + on the right of that first module, search for Omnivery and pick Validate Email. Click Create a connection if you have not linked your account yet, then map the email address from the first module.

  3. 03

    Add Send a Message

    Click the + again and choose Send a Message. Fill its fields with data mapped from the earlier modules, so each contact gets a message built from their own details rather than a fixed text.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open each module's bubble to read the bundles it received and confirm that the address check and the message look the way you expect.

  5. 05

    Schedule and switch on

    Set the schedule on the first module; a new scenario runs every 15 minutes by default. Switch the scenario on. From then on, each run uses operations, one per module per bundle, counted on your Make plan.

Triggers

What can start an Omnivery scenario?

1 module starts a scenario when something happens in Omnivery. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Omnivery as soon as it happens.

Omnivery1Watch for Events

Watch for Events

triggerIn the docs only

Watch for Events gives your scenario a starting point inside Omnivery: each new event it finds becomes a bundle that the following modules can act on. It is the only trigger this app offers in Make.

How it fires
scheduled (the documentation does not describe it; the type is inferred from its name). Make checks the app on the scenario's schedule, every 15 minutes by default, and at least 15 minutes apart on the Free plan.
When to use it
pick it when something that happens in Omnivery, not in another app, should set the rest of the scenario in motion.
Watch out
the documentation does not list which events it returns, so run it once and read the bundles before building on them.
Modules

What can Omnivery do in a scenario?

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

Omnivery1

Make an API Call

ActionIn the docs only

Make an API Call lets you reach any endpoint of the Omnivery API from your scenario, using the connection you already set up, so you are not stuck when a named module falls short.

When to use it
reach for it when you need an Omnivery feature that none of the other four actions covers.
Watch out
you build the request yourself, so test it with Run once and read the bundle before mapping anything from it.
Omnivery2

Parse Email

ActionIn the docs only

Parse Email is the Omnivery action to test when an incoming email holds details you want to hand to the next module. Its name points at reading an email, not sending one.

When to use it
add it where a scenario receives mail and the content should feed a later step.
Watch out
the documentation does not describe its output, so check with Run once which values it actually returns before you map them.
Omnivery3

Send a Message

ActionIn the docs only

Send a Message is the action that makes Omnivery deliver something on your behalf, with content you map from earlier modules instead of typing it by hand each time.

When to use it
place it at the end of a flow, once a new contact or an event has been checked and the message is ready to go.
Watch out
every bundle that reaches it triggers a send, so test on your own address with Run once first.
Omnivery4

Suppress Email

ActionIn the docs only

Suppress Email is, as its name says, the action that marks an address in Omnivery as one your sends should skip, so a person who asked out stays out.

When to use it
connect it right after the step that tells you someone should no longer receive mail, for example an event spotted by Watch for Events.
Watch out
the documentation says nothing about reversing a suppression, so confirm the address in the bundle before the scenario goes live.
Omnivery5

Validate Email

ActionIn the docs only

Validate Email, as its name says, checks an address before you use it, so you learn early whether a contact is worth a send. It fits well in front of Send a Message.

When to use it
add it as soon as an address enters your scenario from a form, a spreadsheet or another app.
Watch out
the result format is not documented, so read the bundle from a test run before you decide which addresses move on to the next module.
Need help

Need help automating Omnivery with Make?

A person reads every message.

FAQ

Questions about the Omnivery Make integration

01Is the Omnivery Make integration free?
Yes, on Make's side. Omnivery is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans drop the interval to 1 minute and remove the cap on active scenarios. Usage is counted in operations each month, one operation for each module on each bundle. Your Omnivery account itself is a separate matter that this page does not cover.
02What do you need to connect Omnivery to Make?
An Omnivery account and a Make account. Make's documentation for Omnivery does not list any prerequisite or dedicated connection steps, so the generic flow applies. Add an Omnivery module, click Create a connection, give it a name if you like, then either authorize Make on the Omnivery page or paste the key Omnivery provides, and click Save. The same connection is then reused by every Omnivery module in your scenarios, so you only do this once per account.
03Does the Omnivery trigger in Make work in real time?
No. Watch for Events is treated as a scheduled trigger (Make's documentation does not describe it, so the type comes from its name), marked with the clock badge in the editor. Make checks Omnivery on the scenario's schedule rather than being called the moment something happens. A new scenario runs every 15 minutes by default. On the Free plan, 15 minutes is also the shortest gap between two scheduled runs, while paid plans allow intervals down to 1 minute. Plan your scenario with that delay in mind if a quick reaction matters.
04What if the Omnivery module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the Omnivery API from your scenario with the connection you already have, so you are not limited to the five named actions. Keep in mind that Make's documentation for Omnivery is marked as limited: it gives module names without describing their fields. Before you rely on a module, run the scenario once and read the bundles each module returns, then build the rest of the flow on what you actually see.
05Should you use Make or n8n for Omnivery?
It depends on the tool your team already works in. On Make, Omnivery comes with 6 modules, including a scheduled trigger and a Make an API Call module for anything else. The same app often has an n8n node too, so check that side for the operations you need. Pick the platform where your other scenarios already live, then compare the modules each one offers for your exact Omnivery task rather than relying on general claims about either tool.
Same platform

Other docs you might need on this stack.

Browse all integrations