Resources · Make integration

Iterable Make integrationAutomate Iterable with Make.

Your signups live in one tool and your Iterable audiences in another? The Iterable Make integration gives you 12 modules (9 actions, 3 searches) to keep profiles, lists and events in step. This page shows how to connect the account and build a first useful scenario.

Try the Iterable integration on MakeSee the 12 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Iterable Make integration do for you?

It lets Make write into Iterable for you. A scenario (the automation you build in Make, a chain of bricks called modules) takes data from another tool and creates a user, adds them to a list or records an event in Iterable. Nobody copies contacts by hand anymore.

Trial signups that reach the right audience. A SaaS team can send each new trial account through Create/Update a User, then Add a User to a List, so the onboarding campaign in Iterable starts from fresh data.

Product activity that Iterable can react to. When a customer finishes onboarding in your app or pays an invoice, Track an Event writes that moment on their profile. Search User Events later reads the history back, for a support reply or a report.

Cleaner lists after a campaign. List Users in a List pulls everyone from an audience, Remove a User From List takes out those who converted, and Delete a List clears a one-off list once it served its purpose.

One limit to know up front: Iterable has no trigger in Make, so it never starts a scenario on its own. The scenario starts from another app or from a schedule. Make also flags its Iterable documentation as AI-generated, so check important details on the Iterable side. The same app exists as an Iterable n8n integration, and the n8n vs Make comparison helps you pick a tool. New to the editor? The Make training covers the basics.

Connect

How do you connect Iterable to Make?

  1. 01

    Create an API key in Iterable

    In Iterable, open Integrations > API Keys and click New API Key. Give it a name you will recognize, choose the key type your use needs, click Create, then copy the key shown in the window.

  2. 02

    Open the connection window in Make

    Add any Iterable module to your scenario and click Create a connection. A connection is your Iterable account linked to Make once, then reused by every Iterable module. The Connection name field is optional but handy.

  3. 03

    Paste the key and save

    Paste the API key you copied from Iterable and follow the instructions on screen to finish. From then on, Make can list the Iterable lists it reads, so you pick them in a menu instead of typing them.

First scenario

Your first scenario with Iterable

GoalWhen someone signs up in another tool, Make creates or updates their Iterable profile and adds them to a list.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app where signups happen (a form tool, your shop, your product) and its trigger module.

  2. 02

    Add Create/Update a User

    Click the + on the right of the first module, search Iterable, choose Create/Update a User and link your account with Create a connection. Map the person's details from the first module.

  3. 03

    Add the person to a list

    Add Add a User to a List after it. Once the connection exists, Make shows your Iterable lists, so you just select the audience that should welcome new signups.

  4. 04

    Test with Run once

    Click Run once and create a test signup. Each module shows the bundles it received (a bundle is one item, here one person). Check the profile and the list in Iterable.

  5. 05

    Schedule and switch on

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

Modules

What each Iterable module does

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

Iterable1

Add a User to a List

Action

In Make“Adds/creates a user to the list.”

Puts a person into one of your Iterable lists, and creates the user along the way when Iterable does not know them yet. The audience fills itself, with no CSV export in between.

When to use it
a webinar registration or a trial signup that should land in the matching audience right after it happens.
Watch out
select the list from the menu Make shows once connected, instead of typing a name by hand.
Iterable2

Create a List

Action

In Make“Creates a list.”

Opens a brand new list in Iterable from inside the scenario, ready to receive users from the next module. Handy when audiences follow your projects rather than a fixed setup.

When to use it
a new event or product launch gets its own audience the moment it is created in your planning tool.
Watch out
the module creates a list each time it runs, so keep it away from a flow that runs once per signup.
Iterable3

Create/Update a User

Action

In Make“Creates/updates a user.”

Keeps an Iterable profile in line with your other tools: Make updates the user if they exist and creates them if they do not. One module covers both cases, so there is no need to check first.

When to use it
a customer changes plan or details in your billing or CRM tool and Iterable should follow.
Watch out
map values from the previous module; a value typed by hand stays identical on every run.
Iterable4

Delete a List

Action

In Make“Deletes a list.”

Removes a whole list from your Iterable account. Useful to stop temporary audiences from piling up once a campaign is over and nobody needs them.

When to use it
a one-off event list whose campaign has ended and whose useful contacts already moved elsewhere.
Watch out
a deletion does not come back. Test with Run once on a throwaway list before pointing it at a real audience.
Iterable5

Delete a User

Action

In Make“Deletes a user.”

Erases a user profile from Iterable entirely, not just from one audience. It is the module that answers a clear request to be forgotten by your marketing tool.

When to use it
a customer asks through your support form to have their data removed, and the request should reach Iterable too.
Watch out
there is no undo. To only take someone out of an audience, Remove a User From List is the gentler choice.
Iterable6

Get a User

Action

In Make“Returns a user.”

Fetches one Iterable profile so the next modules can reuse what Iterable knows about that person. Nothing changes in Iterable; the module only reads.

When to use it
before sending a customer record to your CRM or helpdesk, to enrich it with the marketing profile.
Watch out
it returns one person. For everyone in an audience, List Users in a List is the module to pick.
Iterable7

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any endpoint of the Iterable API with the connection you already set up. It is the escape hatch when the other 11 modules stop short of what you need.

When to use it
an Iterable feature you rely on has no dedicated module in Make.
Watch out
you describe the request yourself, so keep the Iterable API documentation open and test the call with Run once before switching the scenario on.
Iterable8

Remove a User From List

Action

In Make“Removes a user from the list.”

Takes a person out of one Iterable list while their profile stays intact. They simply stop receiving what that audience receives.

When to use it
a trial user becomes a paying customer and should leave the trial nurturing list at the moment the payment arrives.
Watch out
the user still exists in Iterable afterwards. Erasing them completely is the job of Delete a User.
Iterable9

Track an Event

Action

In Make“Tracks an event.”

Records an event on a user's Iterable profile, such as a purchase or a finished onboarding that happened in another tool. The moment now sits in their Iterable history, next to everything else they did.

When to use it
your product or shop knows about a key action that Iterable never sees on its own.
Watch out
every event sent is one operation, so a busy source quickly adds up on your Make plan.
Iterable10

List Users in a List

Search

In Make“Returns all users within a list.”

Returns every user of an Iterable list, each one as a separate bundle. Whatever follows in the scenario then runs person by person.

When to use it
copying an audience to a spreadsheet for a review, or checking each member against your CRM after a campaign.
Watch out
the modules placed after it run once per user, and each of those runs counts as an operation.
Iterable11

Search Lists

Search

In Make“Searches lists.”

Looks through the lists of your Iterable account and hands back the ones found. It lets a scenario pick its target list on the fly instead of relying on a fixed choice.

When to use it
several event or product audiences exist and the right one depends on the incoming data.
Watch out
a search can return zero, one or several lists; plan what the scenario does when nothing matches.
Iterable12

Search User Events

Search

In Make“Returns events for a specific user.”

Reads back the events stored for one specific user in Iterable. It gives the next modules a history of what that person did, not just who they are.

When to use it
a support agent or a report needs the recent activity of a customer before a reply or a decision.
Watch out
expect several bundles, one per event, and the modules that follow will run for each of them.
Need help

Need help automating Iterable with Make?

A person reads every message.

FAQ

Questions about Iterable and Make

01Is the Iterable Make integration free?
Yes, Iterable is a standard app in Make, so it is available from the Free plan. That plan keeps 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) drop the interval to 1 minute, remove the cap on active scenarios and count usage in credits per month. Your Iterable subscription is a separate matter, handled on the Iterable side.
02What do you need to connect Iterable to Make?
An active Iterable account and an API key. In Iterable, go to Integrations, then API Keys, click New API Key, give it a name, choose the type you need, click Create and copy the key from the window. In Make, add an Iterable module, click Create a connection, optionally name it, then paste the key. The same connection then serves all 12 Iterable modules, so the setup happens only once per account.
03Does Iterable trigger a Make scenario in real time?
No, because Iterable has no trigger module in Make: all 12 modules are actions or searches. A scenario that uses Iterable starts somewhere else. Either the trigger of another app opens the flow (a form, a shop, your product), or you set a schedule on the first module, every 15 minutes by default. How fast the scenario reacts then depends on that first module, not on Iterable. Iterable itself then only receives the data.
04What if the Iterable module you need is missing?
It depends on what you need. The 9 actions and 3 searches cover users, lists and events. For anything else, the Make an API Call module reaches any endpoint of the Iterable API with the connection you already have, as long as you know which request to send. Make also marks its Iterable documentation as AI-generated, so confirm important details with the Iterable documentation before you rely on them. The call uses one operation, like any module.
05Make or n8n for Iterable?
It depends on the tool you already use. Iterable is available on both, and the site has a separate guide for the n8n side. In Make, you get 12 ready-made modules for users, lists and events, plus Make an API Call for the rest, all through one connection. If your other automations already run in Make, staying there keeps everything in one place. The n8n vs Make comparison linked above goes through the broader criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations