Resources · Make integration

Enginemailer Make integrationAutomate Enginemailer with Make.

Your mailing list can keep itself tidy while you work on the emails. The Enginemailer Make integration gives you 14 modules: 7 triggers that watch your subscribers and 7 modules that add, tag, find or remove them. This page shows how to plug in your API key and build a first scenario that works.

Try the Enginemailer integration on MakeSee the 14 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Enginemailer Make integration do for you?

The Enginemailer Make integration links your Enginemailer account to Make, a no-code tool where you chain apps together. You build a scenario (the automation itself), made of modules (one brick each: a trigger, an action or a search), and Make moves your subscribers between Enginemailer and your other tools without copy and paste.

Sign-ups that land in the right segment. A contact fills in a form in another app, Add or Update a Subscriber puts them in Enginemailer and Tag a Subscriber to a Subcategory files them where your campaigns expect them. No CSV import, no forgotten tag.

A CRM that knows who left. Watch Unsubscribed Subscriber and Watch Deleted Subscriber hand each departure to the rest of your stack, so sales stops chasing someone who opted out. Useful for a small team that runs its newsletter and its pipeline from different tools.

Follow-up once an autoresponder ends. Watch Subscriber Completed Autoresponder tells Make a contact reached the end of a sequence, which is a clean moment to create a task or notify an account manager.

Limits worth knowing: Make's docs give no type badge for the 7 triggers, and their names point to scheduled triggers, so expect Make to check Enginemailer on the scenario's clock (every 15 minutes by default) instead of hearing about changes instantly. The official Make page for this app is flagged as AI-generated from the Enginemailer docs, so check anything critical against Enginemailer itself. Enginemailer may also have a node in n8n; if you are weighing both tools, the n8n vs Make comparison lays out the criteria. To learn the editor properly, see the Make training, and before picking a plan, read Make pricing.

Connect

How do you connect Enginemailer to Make?

  1. 01

    Copy your API key in Enginemailer

    You need an active Enginemailer account. Open the account dropdown in the top navigation bar, choose Manage account, then API Keys in the left sidebar. Copy the key shown in the API Keys section and keep it at hand.

  2. 02

    Add an Enginemailer module in Make

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

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when you manage several accounts. Paste the API key you copied, follow the on-screen instructions and save. Make can now read and write your subscribers.

First scenario

Your first scenario: form sign-ups filed in the right Enginemailer segment

GoalWhen a new contact arrives from another app, Make adds them to Enginemailer and tags them into the right subcategory.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app your contacts come from, such as your form tool, and choose its trigger so the flow starts there.

  2. 02

    Add the subscriber to Enginemailer

    Click the + to the right of that first module, search for Enginemailer and pick Add or Update a Subscriber. Select your connection, then map the contact's email from the form data.

  3. 03

    Tag them into a subcategory

    Add Tag a Subscriber to a Subcategory after it. Map the same email and choose the subcategory from the list Make offers once the connection works. This is what routes the contact to the right campaigns.

  4. 04

    Test with Run once

    Submit a test entry in your form, then click Run once. Each module shows the bundles it received (a bundle is one item passing through, here one contact). Check that the subscriber and the tag both appear in Enginemailer.

  5. 05

    Schedule and switch it on

    Click the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. Each module run on a bundle counts as one operation on your Make plan.

Triggers

Enginemailer triggers in Make

7 modules start a scenario when something happens in Enginemailer. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Enginemailer as soon as it happens.

Enginemailer1Watch Deleted Subscriber

Watch Deleted Subscriber

triggerIn the docs only

This trigger gives you a heads-up when a contact is removed from your Enginemailer list, so the tools around it can forget that person too. The module name is the only description Make publishes, so treat it as your guide to what it picks up.

How it fires
scheduled, Make checks the app on the scenario's schedule, 15 minutes by default on a new scenario.
When to use it
a colleague cleans the list in Enginemailer and you want the matching record flagged in your CRM or spreadsheet.
Watch out
run the scenario once before trusting it and look at the bundle, since the fields it returns are not documented.
Enginemailer2Watch New Subscriber

Watch New Subscriber

triggerIn the docs only

Start a scenario for each person who joins your Enginemailer list, which is the natural entry point for welcome tasks outside email. Each new contact reaches the next module as its own bundle, so everything after it runs once per person.

How it fires
scheduled, Make checks the app on the scenario's schedule rather than waiting for a push from Enginemailer.
When to use it
copy every sign-up into your CRM, or ping sales in a chat app when someone new subscribes.
Watch out
each contact costs operations in every module that follows, so keep the chain short on a Free plan.
Enginemailer3Watch Subscriber Completed Autoresponder

Watch Subscriber Completed Autoresponder

triggerIn the docs only

Know when a subscriber reaches the end of one of your Enginemailer autoresponder sequences and act on it elsewhere. That end point is often the right moment for a human to step in, after the automated emails have done their part.

How it fires
scheduled, Make checks the app on the scenario's schedule and picks up the contacts that finished since the last check.
When to use it
an onboarding sequence ends and you want a follow-up task created for the account manager.
Watch out
the Make docs give no description of this module, so confirm with Run once which sequence information comes through.
Enginemailer4Watch Subscriber Triggered Autoresponder

Watch Subscriber Triggered Autoresponder

triggerIn the docs only

See the moment a subscriber enters an autoresponder, rather than when they leave it. That gives you a record of who started which sequence, handy when you report on campaigns outside Enginemailer.

How it fires
scheduled, Make checks the app on the scenario's schedule, so the start is noticed at the next check, not the second it happens.
When to use it
log each sequence start in a sheet, or mark the lead as "in nurture" in your CRM.
Watch out
pair it with the Completed trigger only in separate scenarios, and test each one alone to read what it returns.
Enginemailer5Watch Tagged Subscriber

Watch Tagged Subscriber

triggerIn the docs only

React when a subscriber gets a tag in Enginemailer. Tags often encode intent (a product interest, a lead stage), so this trigger turns a label set by a marketer into an action in another tool.

How it fires
scheduled, Make checks the app on the scenario's schedule and collects the tagging events since the previous run.
When to use it
a contact is tagged as a hot lead and you want a deal opened in your CRM.
Watch out
if the same scenario also runs Tag a Subscriber to a Subcategory, check with Run once that your own tagging does not start the scenario again.
Enginemailer6Watch Unsubscribed Subscriber

Watch Unsubscribed Subscriber

triggerIn the docs only

Catch every opt-out so your other tools respect it too. An unsubscribe that only lives in Enginemailer is easy to miss when sales or support write from somewhere else.

How it fires
scheduled, Make checks the app on the scenario's schedule, which means a short lag between the click and the update in your other apps.
When to use it
set a "do not email" flag in your CRM, or remove the person from an audience in an ads tool.
Watch out
an unsubscribe is not a deletion; use Watch Deleted Subscriber for contacts removed from the list entirely.
Enginemailer7Watch Updated Subscriber

Watch Updated Subscriber

triggerIn the docs only

Keep other tools in step when a subscriber's details change in Enginemailer. It saves you from fixing the same typo or new company name in two places.

How it fires
scheduled, Make checks the app on the scenario's schedule and passes along the contacts changed since the last run.
When to use it
a subscriber corrects their name through a preference form and your CRM should show the new version.
Watch out
avoid pairing it with Add or Update a Subscriber on the same contacts in one scenario, or each update you write could be picked up as a fresh change.
Modules

Enginemailer modules in Make

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

Enginemailer1

Add or Update a Subscriber

ActionIn the docs only

Get a contact into Enginemailer without worrying whether they already exist: as its name says, the module adds new people and updates the ones already on your list. It is the workhorse of most sign-up scenarios.

When to use it
a lead comes from a form, a shop or a CRM and must end up on your list.
Watch out
map the email carefully, since it is how you recognize the contact.
Enginemailer2

Deactivate a Subscriber

ActionIn the docs only

Take a contact out of circulation without the finality of a delete. Judging by the name, the record stays in Enginemailer, which leaves room to change your mind.

When to use it
a customer cancels their account in another tool and should stop getting campaigns.
Watch out
the Make docs do not spell out what deactivation changes in Enginemailer, so test it on one contact of your own first.
Enginemailer3

Delete a Subscriber

ActionIn the docs only

Remove a contact from Enginemailer for good, which is the right answer to an erasure request coming from another system. Choose it over Deactivate a Subscriber only when keeping the record is not an option.

When to use it
a data deletion request is logged in your helpdesk.
Watch out
a deletion cannot be undone from Make, so place a filter before it.
Enginemailer4

Find a Subscriber

SearchIn the docs only

Look a contact up in Enginemailer before you act, so the next modules work on the right person. Being a search, it can return zero, one or several bundles, and the rest of the scenario runs once per result.

When to use it
check whether a buyer is already subscribed before sending anything.
Watch out
plan the empty case, or the next modules simply receive nothing.
Enginemailer5

Make an API Call

ActionIn the docs only

Reach any part of the Enginemailer API that the other modules do not cover, with the same connection you already set up. It is your way out when a listed module falls short.

When to use it
you need an Enginemailer feature that has no dedicated module in Make.
Watch out
you write the request yourself, so keep the Enginemailer API docs open next to the scenario.
Enginemailer6

Send Email

ActionIn the docs only

Have Enginemailer send an email as a step of your scenario, so a message goes out the moment something happens in another app. The sending stays with Enginemailer; Make only decides when.

When to use it
an order or a booking elsewhere should trigger a message to that customer.
Watch out
the Make docs list no fields for it, so open the module to see what it asks for before planning around it.
Enginemailer7

Tag a Subscriber to a Subcategory

ActionIn the docs only

File a contact into an Enginemailer subcategory, so your segments fill up from data held in other tools. It pairs naturally with Add or Update a Subscriber right before it.

When to use it
a buyer of a given product should land in the matching interest group.
Watch out
if another scenario watches tagged subscribers, check that the two do not keep starting each other.
Need help

Need help automating Enginemailer with Make?

A person reads every message.

FAQ

Enginemailer and Make: frequent questions

01Is the Enginemailer Make integration free?
Yes, on the Make side. Enginemailer is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run and files up to 5 MB. Paid plans (Core, Pro, Teams, Enterprise) bring the interval down to 1 minute and lift the limit on active scenarios. Usage is counted in operations, one per module per bundle. You still need an active Enginemailer account, whose pricing is set by Enginemailer.
02What do you need to connect Enginemailer to Make?
An active Enginemailer account and its API key. In Enginemailer, open the account dropdown in the navigation bar, click Manage account, then API Keys in the left sidebar, and copy the key. In Make, add any Enginemailer module, click Create a connection, give it a name if you like and paste the key. That single connection then serves all 14 Enginemailer modules in every scenario you build, so you only do this once per account.
03Do Enginemailer triggers in Make work in real time?
Most likely not. The Make docs only list the 7 Enginemailer triggers by name, and those names point to scheduled triggers: Make checks Enginemailer on the scenario's schedule instead of being called by the app. A new scenario checks every 15 minutes by default. On a paid plan you can go down to 1 minute, while the Free plan keeps 15 minutes as the minimum. So a change made in Enginemailer reaches your other tools at the next check, not the second it happens.
04What if an Enginemailer module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the Enginemailer API from your scenario with the same connection, so you are not limited to the 14 listed modules. You write the request yourself from the Enginemailer API documentation. Keep in mind that Make flags its page for this app as AI-generated from the vendor docs, so if a module behaves differently than expected, check with Enginemailer directly before building around it.
05Should you use Make or n8n for Enginemailer?
It depends on which tool your team already works in. Enginemailer has 14 modules in Make, including 7 triggers that appear to be scheduled and an API call module, and an app like this often has an n8n node too. Make lets you start from the Free plan, in an editor where each module shows what it received after Run once. Compare which subscriber events and actions each tool covers for your case, then pick the one where the rest of your automations already live.
Same platform

Other docs you might need on this stack.

Browse all integrations