Resources · Make integration

Emma Make integrationAutomate Emma with Make.

Can Make keep your Emma audience in step with your other tools? The Emma Make integration gives you 32 modules, including 20 instant triggers, for members, groups, fields and messages. This guide helps marketers connect the account and build a first working scenario.

Try the Emma integration on MakeSee the 32 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Emma Make integration let you automate?

The Emma Make integration links your Emma account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a trigger, an action or a search. Emma events such as a sign-up, an opt-out or a click start the scenario, and Make carries the data to your other apps, or back into Emma.

Opt-outs respected everywhere. Watch Member Opted Out hands each unsubscribed contact to your scenario, which can flag them in the CRM your sales team emails from. One unsubscribe, one update, no spreadsheet to reconcile later.

Hot leads sent to sales. Watch Message Clicked fires when a reader clicks a link in your campaign. Chain Get an Audience Member to pull the contact's details and create a task for the account owner in another app.

Registrations without duplicates. A webinar or store tool starts the scenario, Search Audience Members checks whether the person is already known, and Create an Audience Member adds the ones who are new.

Every trigger of this app is instant: Emma calls Make as soon as the event happens, with no polling schedule. Make's documentation lists no numeric limit for Emma, and when a task has no dedicated module, Make an API Call reaches the Emma API with the same connection. If your team also looks at n8n, the n8n vs Make comparison lays out the criteria. Plan costs are detailed in Make pricing, and Make training covers scenario building step by step.

Connect

How do you connect your Emma account to Make?

  1. 01

    Generate your API keys in Emma

    Log in to Emma, open the menu under your name and follow Profile > API Key > Generate API Key. Emma shows a Public API Key, a Private API Key and your Account ID. Copy all three into a safe place right away.

  2. 02

    Open the connection window in Make

    In your scenario, add any Emma module and click Create a connection. A connection is your Emma account linked to Make once, then reused by every Emma module. Give it a clear name in the Connection name field.

  3. 03

    Paste the three values and confirm

    Fill in Account ID, Public API Key and Private API Key with what you copied from Emma, then click Continue. Make now lists your groups and members in the module fields.

First scenario

Your first scenario: form sign-ups into your Emma audience

GoalWhen someone fills in a form in another app, Make adds them to Emma as a new audience member.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. The first module you pick will start everything, so choose the form tool your visitors already use.

  2. 02

    Set up the form trigger

    Search the form app by name, pick its module for new submissions and connect your account. Make then lists the forms it can read, and you choose the one that collects sign-ups.

  3. 03

    Add Create an Audience Member

    Click the + to the right of the form module, search Emma and choose Create an Audience Member. Select the connection you made earlier, then map the form answers into the fields Make shows.

  4. 04

    Test with Run once

    Click Run once, then submit a test entry in your form. Each module shows the bundle it received, one item passed along the chain. Check that the new contact appears in Emma.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set Scheduling: a new scenario checks every 15 minutes by default. Then switch the scenario on so it keeps running without you.

Triggers

Emma triggers: what can start your scenario

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

Emma1Watch New Group

Watch New Group

Instant trigger

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

Every group someone adds in Emma lands in your scenario as a bundle, one item passed from module to module, so a fresh segment never slips by unnoticed. You can log it, announce it or copy it into another tool.

How it fires
instant. Emma calls Make through a webhook as soon as the group exists.
When to use it
several marketers build segments in the same account and the ops lead wants a shared register of every new group.
Emma2Watch Group Updated

Watch Group Updated

Instant trigger

In Make“Triggers when a group has been updated.”

This trigger tells your scenario that an existing group changed, which keeps any copy of your segments in a sheet or a CRM in step with Emma. It covers edits to groups you already have.

How it fires
instant, through a webhook Emma sends when the edit is saved.
When to use it
a group was reworked for a new campaign and the reporting sheet that lists segments should follow without anyone touching it.
Watch out
brand-new groups belong to Watch New Group; keep the two in separate scenarios if they lead to different actions.
Emma3Watch Group Deleted

Watch Group Deleted

Instant trigger

In Make“Triggers when a group has been deleted.”

When a group disappears from Emma, your scenario hears about it and can clean up whatever depended on it elsewhere: a row in a tracking sheet, a tag in another app, a note to the person who owned the segment.

How it fires
instant. The deletion reaches Make by webhook right after it happens in Emma.
When to use it
your team mirrors Emma groups in another tool and wants dead segments removed there too, so nobody targets an audience that is gone.
Emma4Watch Member Added to Group

Watch Member Added to Group

Instant trigger

In Make“Triggers when a member has been added to a group.”

Joining a group is often the moment a campaign starts for a contact. This trigger passes that member to your scenario, so the next step (a task, a message in another channel, a CRM update) follows the group change instead of waiting for someone to notice.

How it fires
instant. Emma pings Make by webhook as soon as the member joins the group.
When to use it
a webinar attendees group should hand each new entrant to your sales team the moment they are placed in it.
Emma5Watch New Member

Watch New Member

Instant trigger

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

Each contact created in your Emma audience starts your scenario with that member as its bundle. It is the broadest way to react when your list grows.

How it fires
instant: Emma calls Make through a webhook when the member is created.
When to use it
your CRM should hold every Emma contact, not only the people who subscribed through a form.
Watch out
Watch Member Signed Up covers sign-ups specifically; running both in separate scenarios may process the same person twice, so pick the one that matches your intent.
Emma6Watch Member Opted Out

Watch Member Opted Out

Instant trigger

In Make“Triggers when a member has opted out.”

An opt-out usually has to be respected in every tool that contacts the person, not only in Emma. This trigger hands the member who opted out to your scenario, so your other apps can stop writing to them too.

How it fires
instant, by webhook, as soon as the member opts out.
When to use it
your sales team also emails from a CRM and needs a flag on the contact once they unsubscribe from your newsletters.
Watch out
treat this scenario as critical and keep it switched on, since a missed opt-out lands on a real person.
Emma7Watch Member Deleted

Watch Member Deleted

Instant trigger

In Make“Triggers when a member has been deleted.”

Removing a contact from Emma can set off the same cleanup elsewhere. The scenario receives the deleted member and can erase or flag the matching record in your other tools.

How it fires
instant. Emma notifies Make through a webhook once the member is deleted.
When to use it
a customer asks to be taken off your lists and their data lives in more than one app.
Watch out
a deletion made with the Delete an Audience Member module sends the member to Archived Items in Emma, so the record is not gone from the account.
Emma8Watch Member Removed from Group

Watch Member Removed from Group

Instant trigger

In Make“Triggers when a member has been removed from a group.”

The mirror image of Watch Member Added to Group: your scenario starts when a contact leaves a group, with that member as its bundle. It helps whenever a group stands for a stage, a program or a list of beta testers.

How it fires
instant. A webhook from Emma reaches Make right after the removal.
When to use it
a client leaves the VIP group and the account manager should get a heads-up in the team chat before the next campaign goes out.
Emma9Watch Member Status Updated

Watch Member Status Updated

Instant trigger

In Make“Triggers when a member status has been updated.”

This trigger reacts when a member's status changes and gives your scenario the member concerned, so your reports and other apps reflect the new state.

How it fires
instant: Emma sends the change to Make by webhook as soon as it is recorded.
When to use it
a dashboard in a spreadsheet counts contacts by status and should move each time one of them changes.
Watch out
Make's documentation does not list the possible statuses, so click Run once with a real change and read the bundle before building on a specific value.
Emma10Watch Member Updated

Watch Member Updated

Instant trigger

In Make“Triggers when a member has been updated.”

Edits to a member record, such as a corrected name or a new value in one of your fields, can travel to your other tools through this trigger. The scenario receives the updated member and passes it along.

How it fires
instant; the update reaches Make through a webhook sent by Emma.
When to use it
Emma is where your team fixes contact details, and the CRM should pick up those fixes instead of keeping stale data.
Watch out
for status changes alone, Watch Member Status Updated is the more targeted choice.
Emma11Watch Member Signed Up

Watch Member Signed Up

Instant trigger

In Make“Triggers when a member has signed up.”

This one reacts to people who sign up, which makes it a natural start for a welcome path outside Emma. The new subscriber arrives in your scenario as a bundle, ready to be sent to a CRM or a sales channel.

How it fires
instant. Emma calls Make by webhook the moment the sign-up happens.
When to use it
a sign-up form on your site feeds Emma, and your sales team wants each new subscriber as a lead in their own tool, without an export.
Emma12Watch Import Contacts Finished

Watch Import Contacts Finished

Instant trigger

In Make“Triggers when contacts have been imported.”

Imports bring a batch of contacts in one go. Rather than reacting to each person, this trigger fires when the contact import is done, so your scenario runs once, when the whole import is over.

How it fires
instant, with a webhook sent by Emma when the import completes.
When to use it
after a trade show list is uploaded, the marketing lead gets a message saying the import is finished and the campaign can go out.
Emma13Watch New Field

Watch New Field

Instant trigger

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

Fields shape what you store about each contact in Emma. When someone adds a field, this trigger tells your scenario, which helps keep a data dictionary or a mapping in another tool current.

How it fires
instant. Emma notifies Make through a webhook once the field exists.
When to use it
your CRM sync relies on matching fields, and the person who maintains it needs to hear about a new one before mapping the next scenario.
Emma14Watch Field Updated

Watch Field Updated

Instant trigger

In Make“Triggers when a field has been updated.”

An edited field can quietly disturb a scenario that maps data into it. This trigger warns you by starting a scenario each time a field changes in Emma, and the field arrives as the bundle, so your alert can name it.

How it fires
instant, sent by webhook as soon as the change is saved.
When to use it
several scenarios write into Emma fields and you want a note in the team chat whenever one of those fields is modified, so someone checks the mappings.
Emma15Watch Field Deleted

Watch Field Deleted

Instant trigger

In Make“Triggers when a field has been deleted.”

When a field is removed from Emma, a module that still writes to it may be aiming at something that no longer exists. This trigger gives you the deleted field as a bundle so you can react early.

How it fires
instant. The deletion is pushed to Make by webhook.
When to use it
an admin tidies up the account and the person who owns your automations should learn which field is gone and review the scenarios that used it.
Emma16Watch Message Forwarded

Watch Message Forwarded

Instant trigger

In Make“Triggers when a message has been forwarded.”

A forward means a reader found your email worth passing on. This trigger turns each forward into a bundle in your scenario, so you can spot the contacts who spread your content. Click Run once to see which details come through before you map them.

How it fires
instant: Emma calls Make through a webhook when a forward is recorded.
When to use it
a community manager keeps a list of advocates and wants each contact who forwards a newsletter added to it without exporting reports.
Emma17Watch Message Opened

Watch Message Opened

Instant trigger

In Make“Triggers when a message has been opened.”

Opens are the most common engagement signal, so this trigger can start many runs after a send. Each open reaches your scenario as a bundle you can route to a CRM or a sheet.

How it fires
instant; Emma notifies Make by webhook as soon as an open is recorded.
When to use it
a sales rep wants to know when a prospect opens the proposal email sent through Emma.
Watch out
every module run is an operation counted on your Make plan, so on a large list keep the scenario short.
Emma18Watch Message Clicked

Watch Message Clicked

Instant trigger

In Make“Triggers when a message has been clicked.”

A click shows stronger interest than an open: the reader went to your link. This trigger brings that click into your scenario, where it can become a follow-up task or a lead score in another tool.

How it fires
instant. Emma sends the click to Make through a webhook right away.
When to use it
a click on the pricing link in a campaign should create a call task for the account owner in your CRM.
Watch out
a campaign with several links may start the scenario for each click; test with Run once before routing on a link.
Emma19Watch Message Share Clicked

Watch Message Share Clicked

Instant trigger

In Make“Triggers when a message share button has been clicked.”

Emma messages can carry a share button. This trigger reacts when a reader clicks it, which tells you who showed the intent to share your content.

How it fires
instant, through a webhook call from Emma.
When to use it
you compare interest in sharing with actual shares and want both events logged side by side in a spreadsheet after each campaign.
Watch out
a click on the button is not the same event as a finished share; Watch Message Shared covers that second step, so pair them when you need both.
Emma20Watch Message Shared

Watch Message Shared

Instant trigger

In Make“Triggers when a message has been shared.”

When a message is actually shared, this trigger passes the event to your scenario. It confirms that your content left your list and went in front of new readers, which is worth tracking per campaign.

How it fires
instant: Emma notifies Make by webhook once the share is recorded.
When to use it
your marketing report counts shares per newsletter and should grow on its own each time a subscriber shares one, instead of being filled by hand.
Modules

Emma actions and searches in Make

Emma gives you 12 modules in 3 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Groups

5 modules
Emma1

List Groups

Search

In Make“Retrieves a list of all groups.”

Returns every group in your Emma account, one bundle per group, so the rest of the scenario can work on each of them or pick the one you need.

When to use it
you want a snapshot of all your segments in a spreadsheet, or you need a group ID for a later module and only know the group by sight.
Watch out
each group becomes its own bundle, so every module placed after it runs once per group and counts operations accordingly.
Emma2

Get a Member Group

Action

In Make“Retrieves details of a member group specified by ID.”

Fetches the details of one group when you already hold its ID, for example from a trigger or from List Groups.

When to use it
a trigger gives you a group ID and the next step, a message to your team, needs readable details about that group.
Watch out
it works by ID only; without one, run List Groups first to find the right group.
Emma3

Create Member Groups

Action

In Make“Creates new member groups.”

Adds new groups to your Emma account from a scenario, which saves building segments by hand each time a campaign, event or client appears in another tool.

When to use it
a new event is added to your planning sheet and needs its own Emma group ready for registrants.
Watch out
run it once in a test and check what Emma created before plugging it into a busy trigger, or duplicate groups may pile up.
Emma4

Update a Member Group

Action

In Make“Updates a member group specified by ID.”

Changes an existing group, identified by its ID, so a segment keeps matching reality when its purpose moves on.

When to use it
a project changes in your management tool and the Emma group tied to it should be updated to match.
Watch out
store the group ID where your scenario can reach it, such as a spreadsheet column, because this module targets a group by ID.
Emma5

Delete a Member Group

Action

In Make“Deletes a member group specified by ID.”

Removes a group from Emma by its ID, handy for clearing out segments built for a one-off campaign.

When to use it
an event is marked as closed in your planning tool and its dedicated group has no reason to stay.
Watch out
the documentation does not say whether a deleted group can be restored, so test on a throwaway group first.

Members

5 modules
Emma6

Search Audience Members

Search

In Make“Searches audience members.”

Looks for members in your Emma audience and returns zero, one or several matches, each as its own bundle.

When to use it
before adding a contact from a form, you want to know whether that person is already in Emma so you update rather than duplicate.
Watch out
several matches mean several bundles, and the modules that follow run once for each of them.
Emma7

Get an Audience Member

Action

In Make“Retrieves details of an audience member specified by ID.”

Retrieves one member's details from their ID, typically handed over by a trigger or a search earlier in the scenario.

When to use it
a click trigger starts the scenario and your sales team needs the contact's details in the CRM task you create next.
Watch out
the module expects the member ID; if your scenario holds anything else, run Search Audience Members first.
Emma8

Create an Audience Member

Action

In Make“Creates a new audience member.”

Adds a new contact to your Emma audience from whatever app sits earlier in the scenario: a form, a store, an event tool.

When to use it
people who register for a webinar in another tool should land in Emma without anyone copying them over.
Watch out
if the person may already be in Emma, place Search Audience Members before it to check first.
Emma9

Update an Audience Member

Action

In Make“Updates an audience member specified by ID.”

Edits a member already in Emma, found by ID, so their record follows what changes in your other tools.

When to use it
a customer switches company in your CRM and the Emma record should say the same before the next newsletter.
Watch out
you need the member ID; pair it with Search Audience Members when your other app only knows the person by other details.
Emma10

Delete an Audience Member

Action

In Make“Deletes an audience member specified by ID. The member will be archived and will appear in the account's Archived Items section.”

Takes a member out of your active audience. Emma does not erase them for good: the member is archived and shows up in the account's Archived Items section.

When to use it
a contact is marked as lost in your CRM and should stop receiving your campaigns.
Watch out
since the record is archived rather than erased, check with your team whether that fits a full removal request.

Other

2 modules
Emma11

Trigger a Custom Event

Action

In Make“Sends payload to the Emma's Event API that triggers an automated workflow.”

Sends data to Emma's Event API, which starts an automated workflow inside Emma. It bridges something that happened in another app and an Emma automation.

When to use it
an order is placed in your store and a follow-up sequence built in Emma should start for that buyer.
Watch out
the automated workflow has to exist on the Emma side first; the module only sends the event that sets it off.
Emma12

Make an API Call

Action

In Make“Performs an arbitrary API call.”

Calls any endpoint of the Emma API with the connection you already set up, which covers what the listed modules leave out.

When to use it
you need an Emma operation that has no dedicated module here and the API offers it.
Watch out
you write the request yourself, so keep the Emma API documentation open and test with Run once before switching the scenario on.
Need help

Need help automating Emma with Make?

A person reads every message.

FAQ

Emma and Make: common questions

01Is the Emma Make integration free?
Yes. Emma is a standard app in Make, so its modules are available on the Free plan. That plan allows 2 active scenarios, at least 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) lift the interval to 1 minute and allow unlimited active scenarios. Usage is counted in operations, one per module run, so a busy trigger such as Watch Message Opened is the one to watch on a small plan.
02What do you need to connect Emma to Make?
An Emma account and three values from it: your Account ID, a Public API Key and a Private API Key. You create them in Emma under your profile name, then Profile, API Key and Generate API Key. In Make, the Create a connection window asks for a connection name and those three values before you click Continue. The Private API Key is shown only once, at generation, so copy it immediately. The documentation lists no other prerequisite.
03Do Emma triggers in Make fire in real time?
Yes. All 20 Emma triggers in Make are instant: Emma calls Make through a webhook as soon as the event happens, whether it is a new member, an opt-out, a group change or a click in a message. Your scenario does not wait for a polling interval, unlike a scheduled trigger that Make checks on the clock. The Free plan interval of 15 minutes concerns scheduled runs, not these webhook calls.
04What if an Emma module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Emma API with the connection you already set up, so you stay in the same scenario and the same account. You write the request yourself, which means keeping the Emma API documentation open and testing with Run once before switching the scenario on. Make's documentation gives no numeric limit for Emma, so the practical boundaries come from your Make plan: active scenarios, execution time and operations.
05Make or n8n for Emma?
It depends on the tool your team already builds in. On Make, Emma comes with 32 modules: 20 instant triggers, 10 actions and 2 searches, plus Make an API Call for anything else. That covers members, groups, fields and messages without code. The same app often has an n8n node too; check that the events and actions you need exist there before moving. Pick the platform where your other automations already live, so connections and monitoring stay in one place.
Same platform

Other docs you might need on this stack.

Browse all integrations