Resources · Make integration

Omnisend Make integrationAutomate Omnisend with Make.

Can Make keep your Omnisend contacts and events in sync with the rest of your stack? The Omnisend Make integration gives you 10 modules: 1 trigger, 7 actions and 2 searches. This page walks an ecommerce marketer from the API key to a first working scenario.

Try the Omnisend integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Omnisend Make integration do?

The Omnisend Make integration links your Omnisend account to Make, a no-code tool where you build a scenario (the automation itself, a chain of modules). Each module is one brick: it watches Omnisend for new contacts, creates or updates a contact, or sends a custom event, and hands the result to the next brick.

Feed Omnisend from your signup forms. A lead lands in another app, and Create a Contact adds or updates that person in Omnisend in the same pass. No CSV export, no copy and paste.

Tell Omnisend what a customer just did. With Trigger a Custom Event, a moment that happens outside your store (a booked call, a returned form) reaches Omnisend under the event name you pick.

Push new subscribers to your other tools. Watch New Contacts picks up contacts created in Omnisend, so a sales sheet or a CRM hears about them without anyone retyping.

What the modules do not cover can often be reached with Make an API Call, which talks to the Omnisend API with the same connection. Many apps in Make also exist as an n8n node; the n8n vs Make page lays out the differences. Before you pick a plan, read the Make pricing breakdown, and if you would rather learn the editor step by step, the Make training covers it.

Connect

How do you connect Omnisend to Make?

  1. 01

    Create an API key in Omnisend

    In Omnisend, open Settings, go to the API Keys section and click Create API Key. Give it a name if asked, click Save, then copy the key shown on screen.

  2. 02

    Add an Omnisend module in Make

    In your scenario, add any Omnisend module and click Create a connection. A connection is your Omnisend account linked to Make once, then reused by every Omnisend module you add later.

  3. 03

    Paste the key and save

    Fill Connection name if you want a clear label (it is optional), paste the API key you copied, and confirm. Make then lists your Omnisend data inside the module fields.

First scenario

Build your first Omnisend scenario

GoalWhen a signup arrives in another app, Make creates the contact in Omnisend and sends a custom event for that person.

  1. 01

    Start a new scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app where signups arrive first, such as your form tool, and set up its module.

  2. 02

    Add Create a Contact

    Click the + on the right of the first module, search for Omnisend and choose Create a Contact. Click Create a connection and paste your API key.

  3. 03

    Map the signup data

    Fill the contact fields by mapping the values from the form module, such as the email and the name. Each signup is a bundle, one item passed from one module to the next.

  4. 04

    Send the custom event

    Add Trigger a Custom Event after the contact module. Pick the event and map the contact from the previous step, so Omnisend receives the event for the right person.

  5. 05

    Test with Run once

    Click Run once, submit a test signup, and open the bundles each module received. Check in Omnisend that the contact and its event are there before going further.

  6. 06

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default) and switch the scenario on. Each module run counts as one operation on your Make plan.

Triggers

What can start an Omnisend scenario?

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

Omnisend1Watch New Contacts

Watch New Contacts

Scheduled trigger

In Make“Triggers when a new contact is created.”

Watch New Contacts starts your scenario with each contact newly created in Omnisend, so the rest of your stack learns about a subscriber without a manual export.

How it fires
this is a scheduled trigger, so Make checks the app on the scenario's schedule, every 15 minutes by default, and picks up the new contacts since the last check.
When to use it
a store owner who wants every fresh subscriber copied into a sales sheet or a CRM the moment the next check runs.
Watch out
it only reacts to new contacts; a contact whose details change later will not start the scenario again.
Modules

What can Make do in Omnisend?

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

Omnisend1

Create a Contact

Action

In Make“Creates or updates a subscriber with all provided values, i.e. name, phone number, tag, etc.”

Create a Contact puts a person into Omnisend with the details you map, and updates that person instead when the contact already exists, so one module covers both cases.

When to use it
right after a signup, a purchase or a lead capture in another app, as the step that brings the person into Omnisend.
Watch out
since it also updates, a wrong mapping can overwrite good data on an existing contact, so test with Run once first.
Omnisend2

Create a Custom Event

Action

In Make“Creates a custom event.”

Create a Custom Event creates a custom event in your Omnisend account from the values you map, so a customer moment tracked elsewhere gets its place in Omnisend.

When to use it
when a new kind of customer moment, such as a webinar signup, should be recorded in Omnisend.
Watch out
Omnisend also has Trigger a Custom Event; compare both on a Run once test and keep the one whose result matches what you expect.
Omnisend3

Get a Contact

Action

In Make“Retrieves information about a specified contact.”

Get a Contact reads one Omnisend contact you already know, and returns its details so the following modules can reuse them without asking you to type anything.

When to use it
a support ticket arrives with a contact reference, and the next step needs that person's details from Omnisend.
Watch out
you need to point it at a specific contact; when you only have partial information, Search Contacts is the better start.
Omnisend4

Get a Custom Event

Action

In Make“Retrieves information about a custom event.”

Get a Custom Event returns the details of one custom event in Omnisend, which helps you check what an event holds before a scenario relies on it.

When to use it
before sending an event from a new scenario, to confirm you picked the right one and see how it is set up.
Watch out
it reads a single event you name; to browse all of them, List Custom Events is the module to open.
Omnisend5

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call lets your scenario reach any endpoint of the Omnisend API, reusing the connection you already created, so you are not stuck when no listed module fits.

When to use it
a task the other nine modules do not cover, once you have found the matching request in the Omnisend API documentation.
Watch out
you write the request yourself here, so Make offers no field list; read the response in the bundle after a Run once test.
Omnisend6

Trigger a Custom Event

Action

In Make“Triggers a custom event in Omnisend.”

Trigger a Custom Event sends one of your custom events to Omnisend for a contact, which is how something that happened outside your store reaches your email marketing.

When to use it
a customer books a call in your scheduling tool, and Omnisend should know about that moment for this person.
Watch out
place it after the module that gives you the contact, otherwise there is no person to send the event for.
Omnisend7

Update a Contact

Action

In Make“Updates a contact module.”

Update a Contact changes the details of a contact that already sits in Omnisend, so the profile stays correct when the information changes somewhere else.

When to use it
a customer edits their phone number in your helpdesk and you want Omnisend to match without a manual fix.
Watch out
it needs an existing contact; pair it with Search Contacts or Get a Contact to find the right one first.
Omnisend8

List Custom Events

Search

In Make“Returns a list of custom events.”

List Custom Events returns the custom events of your Omnisend account, one bundle per event, which gives you an overview of what is already defined.

When to use it
during an audit of your events, to copy them into a sheet and spot the ones nobody sends anymore.
Watch out
each event comes out as its own bundle, so every module placed after it runs once per event and uses operations.
Omnisend9

Search Contacts

Search

In Make“Searches for contacts.”

Search Contacts looks up contacts in Omnisend and hands back what it finds, which lets a scenario check whether a person is already there before acting.

When to use it
before an update, to find the contact behind a new order or form entry.
Watch out
a search can return zero, one or several contacts, so plan what the next module does when nothing or too much comes back.
Need help

Need help automating Omnisend with Make?

A person reads every message.

FAQ

Omnisend and Make: common questions

01Is the Omnisend Make integration free?
Yes, on the Make side. Omnisend is a standard app, available from the Make Free plan. That plan allows 2 active scenarios, a 15 minute minimum between two scheduled runs, 5 minutes of run time at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and allow unlimited active scenarios. You still need your own active Omnisend account, and Omnisend pricing is set by Omnisend, not by Make.
02What do you need to connect Omnisend to Make?
Two things: an active Omnisend account and an API key from that account. In Omnisend, go to Settings, open API Keys, click Create API Key, name it if prompted, save, and copy the key shown on screen. In Make, add an Omnisend module, click Create a connection, optionally fill Connection name, then paste the key. The connection is then reused by every Omnisend module in your scenarios, so you only set it up once.
03Does the Omnisend trigger in Make react instantly?
No. Watch New Contacts is a scheduled trigger: Make checks Omnisend on the scenario's schedule instead of being called the moment a contact appears. A new scenario checks every 15 minutes by default, and that is also the shortest interval on the Free plan. Paid plans can go down to 1 minute between checks. The contacts created since the last check all come out together, one bundle per contact, when the next run starts.
04What if an Omnisend module is missing in Make?
Use Make an API Call. It is part of the 10 Omnisend modules and can call any endpoint of the Omnisend API with the connection you already have, so you are not limited to the 9 other modules. You write the request yourself, based on the Omnisend API documentation, and read the answer in the bundle after a Run once test. If a scenario does not behave as expected, the Make troubleshooting guide on this site is a good place to start.
05Should you use Make or n8n for Omnisend?
It depends on where your other automations already live. On Make, Omnisend comes with 10 modules: a scheduled trigger for new contacts, actions on contacts and custom events, two searches and a generic API call, all usable from the Free plan. Many apps also exist as an n8n node, so check what n8n offers for Omnisend before you decide. The n8n vs Make comparison on this site sets out the criteria side by side, without declaring a winner.
Same platform

Other docs you might need on this stack.

Browse all integrations