Resources · Make integration

Elastic Email Make integrationAutomate Elastic Email with Make.

Can your contact lists and your emails run without you copying anything by hand? The Elastic Email Make integration gives you 15 modules: 2 triggers, 11 actions and 2 searches. This page shows how to link your account, build a first scenario and pick the right module.

Try the Elastic Email integration on MakeSee the 15 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Elastic Email Make integration do for you?

The Elastic Email Make integration links your Elastic Email account to Make, so contacts, lists and emails move on their own. You build a scenario, the automation made of modules chained together, and each module either watches Elastic Email, acts on it or searches it.

Welcome every new subscriber. Watch Contact Added to the List spots the people who joined a list, and Send an Email greets each one. Nobody on the team has to remember to write that first message.

Keep the list in step with your other tools. When a lead signs up through a form or lands in your CRM, Create a Contact files it in Elastic Email and can drop it into a list at the same time. When the same person opts out elsewhere, Unsubscribe a Contact records the choice so your next send respects it.

Keep a record of every campaign sent. Watch Campaign Sent picks up every campaign that went out; pair it with the Airtable Make integration to keep a table of what was sent and when.

The listed modules do not cover the whole Elastic Email API. For anything else, Make an API Call reuses your connection to reach any endpoint. Many apps also have an n8n node; the n8n vs Make comparison lays out how the two tools differ. If Make itself is new to you, the Make training starts from the basics.

Connect

How do you connect Elastic Email to Make?

  1. 01

    Create an API key in Elastic Email

    In Elastic Email, open the Settings panel, choose API, then click Create API Key. Set the permissions, add IP restrictions if you need them, click Create and copy the key shown in the window.

  2. 02

    Add an Elastic Email module in Make

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

  3. 03

    Paste the key and save

    Give the connection a name in Connection name if you like, which helps when you manage several accounts. Paste the API key you copied, confirm, and Make can now read and write in your Elastic Email account.

First scenario

Your first scenario: greet every new contact

GoalWhen a contact is added to an Elastic Email list, Make sends that person a welcome email.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + in the middle of the editor. Search for Elastic Email and choose Watch Contact Added to the List.

  2. 02

    Connect and pick the list

    Click Create a connection and paste your API key. Once connected, Make shows the lists it can read: select the one new subscribers join.

  3. 03

    Add Send an Email

    Click the + on the right of the trigger and pick Send an Email. Fill its fields by mapping the new contact's email address from the trigger, then write your welcome message.

  4. 04

    Test with Run once

    Add a test contact to the list, then click Run once. Open each module to read the bundle it received, a bundle being one item passed along, here one contact, and check the email arrived.

  5. 05

    Schedule and switch on

    Click the clock on the first module. A new scenario checks every 15 minutes by default; the Free plan cannot go below that, paid plans can go down to 1 minute. Then switch the scenario on.

Triggers

What starts an Elastic Email scenario

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

Elastic Email1Watch Campaign Sent

Watch Campaign Sent

Scheduled trigger

In Make“Triggers when a new campaign is sent.”

This trigger hands your scenario each campaign that Elastic Email has sent, so whatever should follow a send can happen without you watching the dashboard. Each campaign arrives as one bundle that the next modules can read.

How it fires
it is a scheduled trigger, so Make checks Elastic Email on the scenario's schedule, every 15 minutes by default, and picks up the campaigns sent since the last check.
When to use it
to log each send in a table, alert the sales team that a promotion just went out, or open a follow-up task in your project tool.
Watch out
a campaign shows up at the next check, not the second it leaves, so plan any follow-up with that gap in mind.
Elastic Email2Watch Contact Added to the List

Watch Contact Added to the List

Scheduled trigger

In Make“Triggers when a new contact is added to the list.”

Pick a list and this trigger gives you every contact that joins it, ready to be greeted, copied into your CRM or flagged to a teammate. You choose the list when you set up the module, once the connection exists.

How it fires
scheduled. Make checks the list on the scenario's schedule and returns the contacts added since the previous run, one bundle per contact.
When to use it
a newsletter list fed by your site's signup form, where each newcomer deserves a welcome message or a record in your sales pipeline.
Watch out
each contact counts as its own bundle, so every module after the trigger spends one operation per new contact.
Modules

Every Elastic Email module in Make

Elastic Email gives you 13 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Elastic Email1

Create a Contact

Action

In Make“Adds a new contact and optionally to one of your lists.”

Adds a person to your Elastic Email account from any other app, and can place that person in one of your lists in the same step. Your audience grows without a CSV import.

When to use it
a lead fills in a form or appears in your CRM and should start receiving your emails.
Watch out
choose the list here if you want the contact in it right away; otherwise the contact exists in the account but in no list.
Elastic Email2

Create a List

Action

In Make“Creates a new list, based on the filtering rule or list of IDs.”

Builds a new list for you, either from a filtering rule or from a set of contact IDs you pass it. Handy when a group of people needs its own sends.

When to use it
a new event, product or webinar calls for a dedicated audience that the scenario can then fill.
Watch out
a list built from IDs needs those IDs first, so place Search Contacts before it to collect them.
Elastic Email3

Delete a Contact

Action

In Make“Permanently deletes the contacts provided. You can provide either a qualified rule or a list of emails.”

Removes contacts from your account for good. You give it either a rule that selects them or a list of email addresses.

When to use it
someone asks to have their data erased, and the request reaches you through a form or a support ticket.
Watch out
the deletion is permanent. If the goal is only to stop sending, Unsubscribe a Contact keeps the record and its history.
Elastic Email4

Delete a List

Action

In Make“Deletes a list and removes all the contacts from it (does not delete contacts).”

Clears away a list you no longer need. The contacts it held stay in your account; only the list and its memberships disappear.

When to use it
an event is over and its temporary list would only clutter the account.
Watch out
any scenario still pointing to that list, such as Watch Contact Added to the List, should be pointed to another list first, so check your scenarios before deleting.
Elastic Email5

Get a Contact

Action

In Make“Loads detailed contact information.”

Brings back the full details of one contact, so the next modules can read everything Elastic Email knows about that person.

When to use it
before updating a record or routing a reply, when you need the current status of the contact rather than what another app remembers.
Watch out
it targets a single contact; to go through a group, start from Search Contacts instead.
Elastic Email6

Get a List

Action

In Make“Gets detailed information about specific list.”

Returns the details of one specific list, which lets a scenario check what the list looks like before acting on it.

When to use it
a report or a Slack message should describe a list, or a later module needs information that only the list itself holds.
Watch out
you must already know which list you want; when you do not, Search Lists finds it first.
Elastic Email7

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any endpoint of the Elastic Email API with the connection you already set up, so you are not stuck when no ready-made module fits.

When to use it
the action you need is part of the Elastic Email API but has no module of its own in Make.
Watch out
you write the request yourself, so keep the Elastic Email API documentation open while you set it up.
Elastic Email8

Send an Email

Action

In Make“Submits the emails.”

Sends an email through Elastic Email straight from your scenario, with a message built from data that earlier modules gathered.

When to use it
a welcome message, an order confirmation or a reminder that must go out as soon as something happens in another tool.
Watch out
each bundle reaching this module sends one email, so filter upstream if only some items should trigger a message.
Elastic Email9

Unsubscribe a Contact

Action

In Make“Manually adds or updates a contact to Unsubscribed status.”

Marks a contact as Unsubscribed, adding the person with that status if they were not in the account yet. Your sends then stop reaching them.

When to use it
someone opts out in your CRM, your shop or a support conversation, and Elastic Email must hear about it too.
Watch out
the record stays in the account; reach for Delete a Contact only when the person asked to be erased.
Elastic Email10

Update a Contact

Action

In Make“Updates a selected contact.”

Changes the information of a contact who is already in Elastic Email, so your lists reflect what your other tools know today.

When to use it
a customer edits a profile in your app or a deal moves forward in the CRM, and the email side should follow.
Watch out
the contact must exist first; if you are not sure, run Get a Contact or Search Contacts beforehand.
Elastic Email11

Update a List

Action

In Make“Updates an existing list.”

Edits a list that already exists instead of creating a second one, which keeps your account tidy as audiences change.

When to use it
a segment gets renamed or its scope shifts after a product change.
Watch out
find the list with Search Lists first when the scenario does not already know which one to edit.
Elastic Email12

Search Contacts

Search

In Make“Searches the contacts or lists them all .”

Looks through your contacts, or returns all of them, and hands each match to the next module as its own bundle.

When to use it
you need to run the same action on a whole group, such as copying the contacts into a spreadsheet or updating them one by one.
Watch out
the result can hold zero, one or many contacts, and each one costs an operation in every module that follows.
Elastic Email13

Search Lists

Search

In Make“Searches the lists or lists them all.”

Finds lists in your account, or returns every one of them, which is how a scenario learns which lists exist without you typing their names.

When to use it
building an overview of your audiences, or locating a list before Get a List or Update a List.
Watch out
the search can return zero, one or many lists, and each list found runs the following modules once.
Need help

Need help automating Elastic Email with Make?

A person reads every message.

FAQ

Elastic Email and Make: common questions

01Is the Elastic Email Make integration free?
Yes. Elastic Email is a standard app in Make, so it works 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, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. Make counts usage in operations, one per module run on one bundle. Your Elastic Email subscription is separate and handled on their side.
02What do you need to connect Elastic Email to Make?
An active Elastic Email account and an API key. You create the key in Elastic Email under Settings, then API, then Create API Key, where you also set its permissions and optional IP restrictions. Copy the key shown after you click Create. In Make, add any Elastic Email module, click Create a connection, name it if you wish and paste the key. That single connection then serves every Elastic Email module in your scenarios.
03Do the Elastic Email triggers in Make work in real time?
No. Both triggers, Watch Campaign Sent and Watch Contact Added to the List, are scheduled. Make checks Elastic Email on the scenario's schedule, which is every 15 minutes by default for a new scenario. On the Free plan, 15 minutes is also the shortest possible interval; paid plans can go down to 1 minute. Each campaign or contact reaches the scenario as its own bundle at the next check, so expect a short wait between the event and the reaction.
04What if an Elastic Email module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Elastic Email API through the connection you already set up, so you can cover actions that the 15 listed modules do not offer. You write the request yourself, which means reading the Elastic Email API documentation. The Make documentation for this app lists no specific limit, and it is flagged as AI-generated content, so double-check important details with Elastic Email directly.
05Should you use Make or n8n for Elastic Email?
It depends on the tool your team already knows. Make offers 15 ready modules for Elastic Email, with two scheduled triggers and Make an API Call for the rest, and it runs on the Free plan for a first test. Many apps also have an n8n node, so check whether one exists for Elastic Email and compare what it covers with the modules listed here. Pick the tool whose editor you are comfortable maintaining over time rather than the one with the longest feature list.
Same platform

Other docs you might need on this stack.

Browse all integrations