Resources · Make integration

Emercury Make integrationAutomate Emercury with Make.

Can Make keep your Emercury lists clean without a single export? The Emercury Make integration gives you 7 action modules for audiences, subscribers and suppressions. This guide is for email marketers: link your account, then build a first scenario step by step.

Try the Emercury integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Emercury Make integration do?

The Emercury Make integration links your Emercury email account to Make, a no-code tool where you build a scenario (the automation itself, a chain of bricks called modules). Other apps feed it data, and Emercury receives the result: a new audience, an updated subscriber, a fresh suppression entry.

Suppressions that follow your CRM. When a contact asks to stop hearing from you in another tool, a scenario can pass that address to Add Suppression, so Emercury stops mailing it without anyone copying lists by hand.

Subscriber records that stay current. A signup form or a sales app sends the latest details, Get Audience points to the right audience, and Update Subscriber writes the change into Emercury.

Unsubscribes pushed back to the rest of your stack. Get Unsubscribed and Get Suppressions read who left or who is blocked, and the next module tells your CRM or a spreadsheet.

What Make cannot do here: Emercury has no trigger module in Make, so nothing starts from an Emercury event. Every scenario opens on another app or on a schedule. There is no Make an API Call module either, so the 7 modules are the whole toolbox. If you are weighing both tools, the n8n vs Make comparison lays out the criteria, and the Make training covers mapping from scratch. For plan limits, see Make pricing.

Connect

How do you connect Emercury to Make?

  1. 01

    Request your API key in Emercury

    In Emercury, click the settings icon at the top right, open For Developers, then API Management. Click Request API. Once Emercury approves the request, the key shows up in that same section, ready to copy.

  2. 02

    Add an Emercury module in Make

    In your scenario, add any Emercury module and click Create a connection. A connection is your Emercury account linked to Make once, then reused by all 7 modules. The Connection name field is optional; a clear name helps when you run several accounts.

  3. 03

    Paste the key and save

    Paste the API key you copied from Emercury and follow the on-screen instructions to finish. From then on the module can list the Emercury objects it can read, so you pick them instead of typing them.

First scenario

Build your first scenario with Emercury

GoalWhen a contact changes in your CRM, Make finds the right Emercury audience and updates that subscriber.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Since Emercury has no trigger, pick the module of the app where your contacts change, such as your CRM or a form tool.

  2. 02

    Add Get Audience

    Click the + to the right of that first module, search for Emercury, choose Get Audience and click Create a connection. Then select the audience that should receive the update.

  3. 03

    Map the change with Update Subscriber

    Add Update Subscriber next. Map the contact data coming from the first module into the fields Make shows. Each bundle, meaning one contact passing from module to module, becomes one update in Emercury.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario a single time and shows the bundles each module received. Open Emercury to confirm the subscriber changed as expected before going further.

  5. 05

    Schedule and switch it on

    On the first module, open the clock to set the schedule: every 15 minutes by default. Then turn the scenario on. Keep in mind that each module run counts as one operation on your Make plan.

Modules

What can the Emercury modules do?

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

Emercury1

Add Audience

ActionIn the docs only

Add Audience creates a new audience in Emercury from inside a scenario, so a fresh campaign or a new client segment gets its own list without a trip to the Emercury dashboard.

When to use it
when an event elsewhere, like a new product line entered in your CRM, calls for a separate audience.
Watch out
the Make documentation gives no description of its fields, so open the module and read what Make asks for before mapping.
Emercury2

Add Suppression

ActionIn the docs only

With Add Suppression, an address lands on your Emercury suppression list, which means your campaigns stop reaching that contact. It is the module that turns a do-not-contact request in another tool into a block in Emercury.

When to use it
a customer asks your support desk to stop all emails.
Watch out
test it with Run once on your own address first, since a wrong mapping could block real subscribers.
Emercury3

Get Audience

ActionIn the docs only

As its name says, Get Audience fetches one Emercury audience and hands its details to the next module. On its own it changes nothing; its job is to give later modules the right audience to work on.

When to use it
before Update Subscriber or a report, when the scenario needs to know which audience it targets.
Watch out
pick the audience from the list Make shows once the connection exists, rather than typing it.
Emercury4

Get Subscribers

ActionIn the docs only

Pulling contacts out of Emercury is what Get Subscribers is for: it brings subscribers into the scenario so another app, a spreadsheet or a CRM, can receive them without an export file.

When to use it
when your sales team wants the people on an Emercury audience copied into their own tool.
Watch out
the documentation says nothing about how many subscribers come back per run, so check the bundles after Run once.
Emercury5

Get Suppressions

ActionIn the docs only

This module reads your Emercury suppression list, the addresses your campaigns must skip, and passes them on. It keeps other tools aware of who should not be contacted.

When to use it
before a sales team imports leads into another sending tool, to make sure blocked addresses are flagged there too.
Watch out
it only reads the list; to add an address, you need Add Suppression.
Emercury6

Get Unsubscribed

ActionIn the docs only

People who opted out of your Emercury emails come out of Get Unsubscribed, ready to be written somewhere else. Your CRM then shows the same opt-out status as your email tool.

When to use it
when account managers keep emailing contacts who already unsubscribed from your newsletter.
Watch out
Make offers a separate module for unsubscribes and for suppressions, so pick the one that matches the list you mean.
Emercury7

Update Subscriber

ActionIn the docs only

Update Subscriber rewrites an existing Emercury contact with newer details, so segments and personalization rely on current data instead of what the person typed years ago.

When to use it
a customer changes company or job title in your CRM and your emails should reflect it.
Watch out
going by its name, it edits a subscriber already in Emercury; check which fields Make asks for and confirm the result after Run once.
Need help

Need help automating Emercury with Make?

A person reads every message.

FAQ

Emercury and Make: common questions

01Is the Emercury Make integration free?
Yes, on the Make side. Emercury is a standard app, available on the Free plan. That plan allows 2 active scenarios, runs no more often than every 15 minutes, stops each run after 5 minutes and caps data transfer at 512 MB. Paid plans (Core, Pro, Teams, Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one per module run. You still need an active Emercury account, which Emercury bills on its own terms.
02What do you need to connect Emercury to Make?
Two things: an active Emercury account and an API key. The key comes from Emercury itself. Open the settings icon at the top right, go to For Developers, then API Management, and click Request API. Once the request is approved, copy the key shown there. Back in Make, add an Emercury module, click Create a connection, give it a name if you like and paste the key. The same connection then serves all 7 modules.
03Can an Emercury scenario start in real time?
No, not from Emercury. The app has no trigger module in Make, so an Emercury event cannot start a scenario. You have two ways around it. Start on another app, such as the form or CRM where the change happens, and add Emercury modules after it. Or begin with an Emercury module and let Make run the scenario on its schedule, every 15 minutes by default, or every minute at the fastest on a paid plan.
04What if the Emercury module you need is missing?
It depends on the task. The Emercury app in Make has 7 action modules and no Make an API Call module, so there is no generic way to reach other parts of the Emercury API from this app. First check whether two existing modules can be chained, for example Get Audience followed by Update Subscriber. If the task still falls outside those 7, another app or a custom setup is needed, and the team can look at it with you.
05Should you use Make or n8n for Emercury?
It depends on your criteria rather than on the app. In Make, Emercury comes with 7 action modules, a connection through an API key and no trigger, so scenarios start from another app or a schedule. Many apps also have an n8n node, and the right choice comes down to how your team likes to build and who will maintain the scenarios. Compare the modules available on each side for your exact use case before deciding.
Same platform

Other docs you might need on this stack.

Browse all integrations