Resources · Make integration

Mailchimp Make integrationAutomate Mailchimp with Make.

Can Make keep your Mailchimp audience tidy while you do something else? The Mailchimp Make integration gives you 46 modules, 7 of them triggers, for campaigns, subscribers, tags and reports. This guide shows what each one is for and walks you through a first scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Mailchimp Make integration do for you?

It links your Mailchimp account to Make so that audience changes and campaigns can start an automation, or be edited by one. In Make, that automation is a scenario: a chain of modules, each one a single brick (a trigger, an action or a search). You pick the bricks, Make runs them.

Sort new contacts the moment they land. A SaaS team collecting trial signups can start with Watch Subscribers, then use Add/Remove Member Tags to label each person by the form they came from. Nobody opens Mailchimp to tag by hand.

Feed your store orders into Mailchimp. An online shop can send each purchase with Create an Order, so the audience knows who bought, not just who opened. Pair it with Add an Event to log other actions, like a webinar attended.

Pull campaign numbers out of Mailchimp. Watch Campaigns spots a campaign that was created or sent; Get a Campaign Report and List Click Reports then fetch the results, ready to push into a sheet or a dashboard in another app.

Know the edges before you start. The Mailchimp docs in Make give no numeric limit, so plan with your Make plan in mind (see Make pricing). When a Mailchimp feature has no module, Make an API Call reaches the rest of the API with the same connection. The same app also exists in n8n: the Mailchimp n8n integration page covers that side, and n8n vs Make helps you choose.

Connect

How do you connect your Mailchimp account to Make?

  1. 01

    Add a Mailchimp module

    You need a Mailchimp account first, nothing else. In your scenario, add any Mailchimp module and click Create a connection. A connection is your Mailchimp account linked to Make once, then reused by every Mailchimp module you add.

  2. 02

    Name it and save

    Type a label in Connection name if you juggle several accounts, for example one per client audience. It is optional. Then click Save and leave the advanced options alone unless you run your own Mailchimp app.

  3. 03

    Approve access in Mailchimp

    Mailchimp opens a sign-in window when it needs to. Log in to the account that owns the audience and confirm that Make may access it. Back in Make, the module can now list your audiences and campaigns.

First scenario

Build your first scenario: tag every new subscriber

GoalWhen someone joins or is updated in a Mailchimp audience, Make adds a tag to that contact.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big +. Search for Mailchimp and pick Watch Subscribers. Link your account with Create a connection if it is your first Mailchimp module.

  2. 02

    Point the trigger at an audience

    Choose the audience to watch. No need to hunt for its ID: once the connection exists, Make lists the audiences it can read and you just pick one from the dropdown.

  3. 03

    Add the tagging step

    Click the + on the right of the trigger and add Add/Remove Member Tags. Map the email coming from Watch Subscribers into it, then type the tag name you want, such as trial-signup.

  4. 04

    Test with Run once

    Click Run once, then add or edit a test contact in Mailchimp. Each module shows the bundles it received (a bundle is one item passing through, here one contact). Check the tag in Mailchimp.

  5. 05

    Schedule it and switch it on

    Watch Subscribers is a scheduled trigger, so set its clock on the first module. A new scenario checks every 15 minutes by default. Switch the scenario on and it keeps tagging without you.

Triggers

Which Mailchimp triggers can start a scenario?

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

Mailchimp1Watch Campaigns

Watch Campaigns

Scheduled trigger

In MakeTriggers when a new campaign is created or sent.

Starts your scenario each time a campaign is created or sent in Mailchimp, and hands its details to the next module. Handy for keeping a record of every send outside Mailchimp.

How it fires
scheduled. Make checks Mailchimp on the scenario's schedule, so a new campaign shows up at the next check, not the second it is sent.
When to use it
when your marketing lead wants a line in a shared sheet or a message in a team channel for every campaign that goes out.
Watch out
it reacts to creation as well as sending, so add a filter after it if you only care about campaigns that actually went out.
Mailchimp2Watch Subscribers

Watch Subscribers

Scheduled trigger

In MakeTriggers when a new subscriber joins a list or is updated.

Picks up people who join a Mailchimp audience, and also people whose profile changes there. Each one arrives as a separate bundle you can route anywhere.

How it fires
scheduled. Make asks Mailchimp for new or changed subscribers each time the scenario's schedule comes around.
When to use it
a trial signup lands in your audience and your CRM or onboarding tool should hear about it without anyone copying the address.
Watch out
updates count too, so a contact edited several times can come through again; decide whether the next step should create or update.
Mailchimp3Watch Unsubscribes

Watch Unsubscribes

Scheduled trigger

In MakeTriggers when a subscriber unsubscribes from a campaign.

Catches every person who unsubscribes from a campaign and passes their details along, so other tools can respect that choice.

How it fires
scheduled. Make looks for fresh unsubscribes on the scenario's schedule rather than being told by Mailchimp.
When to use it
your sales team works from a CRM and must stop emailing people who opted out of your newsletter.
Watch out
the gap between two checks is the gap before your other tools know. Keep the schedule tight if compliance matters to you.
Mailchimp4Watch List Events

Watch List Events

Instant trigger

In MakeTriggers when one of the defiend events occurs on a list.

Listens to one Mailchimp audience for the events you choose when you set it up, and starts the scenario when one of them happens. It is the only instant trigger of the app.

How it fires
instant. Mailchimp calls Make through a webhook as soon as the event occurs, so there is no schedule to set.
When to use it
a new signup should get a personal follow-up from your team while their interest is still warm.
Watch out
only the events you ticked are sent, so revisit that choice if a case you expected never arrives.
Mailchimp5Watch Lists

Watch Lists

Scheduled trigger

In MakeTriggers when a new list is created.

Notices when someone creates a new audience in your Mailchimp account and passes its details on, which helps you keep your setup consistent.

How it fires
scheduled. Make checks for new audiences on the scenario's schedule.
When to use it
an agency spinning up an audience per client wants the same custom fields added to each one without doing it by hand.
Watch out
it only reacts to creation. Renaming or editing an existing audience will not start the scenario.
Mailchimp6Watch List Segments

Watch List Segments

Scheduled trigger

In MakeTriggers when a segment is created or updated.

Fires when a segment of your audience is created or updated, handing over the segment so the next modules can read its members or record the change.

How it fires
scheduled. Make polls Mailchimp for new or changed segments on the scenario's schedule.
When to use it
your team builds a segment for a product launch and wants its members copied into an ad audience or a spreadsheet.
Watch out
an update fires it again, so a segment edited often can run the scenario more than you expect and use more operations (an operation is one module run on one bundle, what Make counts on your plan).
Mailchimp7Watch Files

Watch Files

Scheduled trigger

In MakeTriggers when a new file is added.

Spots each new file added to Mailchimp's file storage, such as an image uploaded for a campaign, and sends it down the scenario.

How it fires
scheduled. Make checks for new files on the scenario's schedule.
When to use it
designers upload visuals to Mailchimp and you want a copy archived in your cloud drive for other channels.
Watch out
on the Free plan, files over 5 MB can't pass through a scenario, so heavy assets may stop there.
Modules

What else can Make do in Mailchimp?

Mailchimp gives you 39 modules in 13 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Campaign

9 modules
Mailchimp1

Create a Campaign

Action

In MakeCreates a new campaign.

Builds a new Mailchimp campaign from data your scenario already holds, so the draft is waiting for you instead of a blank screen.

When to use it
a new blog post is published and you want a newsletter draft set up for it.
Watch out
creating is not sending. The campaign stays a draft until another step or a person sends it.
Mailchimp2

Update a Campaign

Action

In MakeUpdates an existing campaign.

Changes the settings of a campaign that already exists, like its subject line or audience, without opening the Mailchimp editor.

When to use it
a product name changed in your catalog and every pending draft should pick up the new wording.
Watch out
you need the campaign's ID, so put Search Campaigns or Watch Campaigns before it.
Mailchimp3

Edit a Campaign Template Content

Action

In MakeEdits a defined content area of a custom HTML template.

Rewrites one named content area inside a campaign built on a custom HTML template, leaving the rest of the layout untouched.

When to use it
your digest keeps its design but the featured product block changes with each new launch in your store.
Watch out
it only works with campaigns built on a custom HTML template that defines those areas.
Mailchimp4

Perform a Campaign Action

Action

In MakePerforms a campaign action.

Triggers one of the actions Mailchimp allows on a campaign, which you pick from the module's list once the connection is set.

When to use it
a draft built earlier in the scenario is approved in your project tool and should now move forward in Mailchimp.
Watch out
some actions reach real inboxes. Test on a campaign aimed at a test audience before switching the scenario on.
Mailchimp5

Get a Campaign

Action

In MakeGets metadata of a specified campaign.

Fetches the details of one campaign you already know, such as its subject, audience and status, so later modules can use them.

When to use it
a teammate drops a campaign ID in a form and your scenario needs its settings to fill a report.
Watch out
it returns settings, not results. For opens and clicks, reach for Get a Campaign Report.
Mailchimp6

Get a Campaign Report

Action

In MakeGets a campaign report.

Returns the performance report of a campaign, the numbers your marketing team usually screenshots by hand.

When to use it
a campaign has been out for a while and you want its results written into a client dashboard.
Watch out
the report is a snapshot of the moment the module runs. Running it right after sending gives almost empty figures.
Mailchimp7

Search Campaigns

Search

In MakeSearches for the campaigns.

Looks through your campaigns and returns the ones that match, one bundle per campaign.

When to use it
you need to find a campaign by its name before updating or reporting on it.
Watch out
a search can return zero, one or many results. Plan what the next step does when nothing matches, or when several do.
Mailchimp8

List Campaign Open Details

Search

In MakeLists all campaign open details.

Lists who opened a given campaign, contact by contact, which turns a vague open rate into names you can act on.

When to use it
your sales reps want a follow-up task for every lead who opened the pricing email.
Watch out
each opener becomes its own bundle, and every module after it runs once per bundle, which adds operations fast on large sends.
Mailchimp9

Delete a Campaign

Action

In MakeDeletes a campaign.

Removes a campaign from your Mailchimp account for good.

When to use it
test drafts pile up from your automations and you want them cleared once the real campaign is out.
Watch out
there is no undo in Make. Check the campaign ID with Run once before letting this run on its own.

Merge Fields

5 modules
Mailchimp10

Create a Merge Field

Action

In MakeCreates a new merge field.

Adds a new custom field to an audience, the kind you later drop into emails to personalize them.

When to use it
Watch Lists catches a fresh audience and every one of them should get the same company-size field.
Watch out
run it twice on the same audience and you may end up with two similar fields; check with Search Merge Fields first.
Mailchimp11

Update a Merge Field

Action

In MakeUpdates an existing merge field.

Edits an existing audience field, for example its label or its default value.

When to use it
your team renamed a plan tier and the matching field should follow across every client audience.
Watch out
every audience using that field sees the change, so test on one audience with Run once before looping over all of them.
Mailchimp12

Get a Merge Field

Action

In MakeRetrieves an existing merge field.

Reads one audience field you already know, giving you its settings to reuse or compare.

When to use it
before copying a field setup to a new audience, you pull the original to mirror its type and label.
Watch out
it reads one field only; to see them all, Search Merge Fields is the better fit.
Mailchimp13

Search Merge Fields

Search

In MakeSearches for merge fields or lists them all.

Finds fields on an audience, or lists them all when you leave the search open.

When to use it
an audit scenario checks that each client audience carries the fields your templates expect.
Watch out
every field comes out as its own bundle, so add an aggregator if you want them in one list.
Mailchimp14

Delete a Merge Field

Action

In MakeDeletes an existing merge field.

Removes a custom field from an audience, along with the data stored in it.

When to use it
a one-off event field has served its purpose and clutters every contact profile.
Watch out
the values held in that field go with it, so export them first if anyone might ask.

Subscriber

5 modules
Mailchimp15

Search Subscribers

Search

In MakeSearches for the subscribers.

Looks up contacts across your audience and returns those that match your search, each as a bundle.

When to use it
a support ticket arrives and you want to know whether the sender is already on your list.
Watch out
no match means no bundle, and the modules after it simply don't run. Plan a separate check if the "not found" case matters to you.
Mailchimp16

Get a Subscriber

Action

In MakeGets metadata of a subsciber by email.

Pulls the full profile of one contact from their email address, including the audience fields you store.

When to use it
a deal closes in your CRM and you want the contact's Mailchimp profile before choosing which sequence fits.
Watch out
it looks up one exact email. When the address may be wrong or old, Search Subscribers is the gentler option.
Mailchimp17

Add/Update a Subscriber

Action

In MakeAdds an email address to a subscriber list.

Puts an email address into an audience, or refreshes the contact if it is already there.

When to use it
someone books a demo through your website form and should join the product newsletter.
Watch out
the app also has Add/Update a List Member. Pick one of the two for a given flow and stick to it, so your scenarios stay easy to read.
Mailchimp18

Edit a Subscriber

Action

In MakeEdits an existing subscriber.

Changes the details of a contact already in your audience, without touching their subscription.

When to use it
a customer upgrades their plan in your billing tool and their Mailchimp profile should show it.
Watch out
the contact must exist. For someone who might be new, Add/Update a Subscriber is the safer choice.
Mailchimp19

Delete a Subsciber

Action

In MakeArchives or permanently deletes a subscriber.

Archives a contact or erases them for good, depending on the option you set in the module.

When to use it
a customer asks to have their data removed and your privacy process should reach Mailchimp too.
Watch out
permanent deletion can't be reversed from Make, and the module name really is spelled "Subsciber" in the list.

List

5 modules
Mailchimp20

Search Lists

Search

In MakeSearches for the lists.

Returns the audiences in your account that match a search, one bundle each.

When to use it
an agency scenario needs the right client audience by name before adding contacts to it.
Watch out
similar names can match more than one audience; test with Run once and read which ones came back.
Mailchimp21

Get a List

Action

In MakeGets metadata of a specified list.

Reads the settings and details of one audience you already know.

When to use it
a client report opens with the audience's name and settings pulled straight from Mailchimp.
Watch out
it gives settings, not results. For campaign numbers, go through Get a Campaign Report instead.
Mailchimp22

Create a List

Action

In MakeCreates a new list.

Sets up a brand-new audience in your Mailchimp account from inside a scenario.

When to use it
a new client signs with your agency and their onboarding checklist in your project tool should produce a ready audience.
Watch out
a scenario that runs twice creates two audiences. Check with Search Lists first that the name isn't taken.
Mailchimp23

Update a List

Action

In MakeUpdates an existing list.

Edits the settings of an existing audience, such as its name or default sender details.

When to use it
a client rebrands and every audience you run for them should carry the new company name.
Watch out
test on one audience with Run once first, since a mapping error changes every audience the scenario touches.
Mailchimp24

Delete a List

Action

In MakeDeletes a list.

Removes an entire audience and everything attached to it from Mailchimp.

When to use it
a temporary audience built for a trade show is no longer needed.
Watch out
the contacts inside go with it and nothing in Make brings them back. Keep a human approval step in front of this one.

List Members

1 module
Mailchimp25

Add/Update a List Member

Action

In MakeAdds or updates a list member.

Creates a member in an audience or updates them if the email is already known, in a single step.

When to use it
a checkout in your store should create or refresh the buyer in the customers audience.
Watch out
it overlaps with Add/Update a Subscriber. Choose one per scenario so a teammate reading it later isn't confused.

Segment

3 modules
Mailchimp26

Lists Segment Members

Search

In MakeRetrieves a list of all segment members.

Returns every member of a chosen segment, each as a bundle you can send elsewhere.

When to use it
your "VIP buyers" segment should be mirrored in a Google Sheet your sales team reads.
Watch out
big segments mean many bundles and many operations on your plan for every module that follows.
Mailchimp27

Add a Member to a Segment

Action

In MakeAdds a new member to a static segment.

Drops an existing contact into a static segment, the kind you fill by hand rather than with rules.

When to use it
a customer attends your webinar and should land in the "webinar attendees" segment.
Watch out
it only works on static segments. Rule-based segments decide their members themselves.
Mailchimp28

Remove a Member from a Segment

Action

In MakeRemoves a member from the specified static segment.

Takes a contact out of a static segment while leaving them in the audience.

When to use it
a lead converts into a customer and should leave the "nurture" segment.
Watch out
like its twin, it ignores rule-based segments; the contact stays there as long as the rule matches.

Orders

1 module
Mailchimp29

Create an Order

Action

In MakeCreates a new order.

Sends a purchase into Mailchimp so your audience data reflects what people bought, not only what they opened.

When to use it
a new order in your online shop should show up in Mailchimp for later targeting.
Watch out
map the buyer's email carefully; an order tied to the wrong address teaches Mailchimp the wrong things about your customers.

Activity

2 modules
Mailchimp30

List List's Activities

Search

In MakeRetrieves up to the previous 180 days of daily detailed aggregated activity stats for a list.

Gives you an audience's activity day by day, already summed up: sends, opens, clicks, new subscribers. It goes back up to one hundred eighty days.

When to use it
a client dashboard should chart how the audience behaves without anyone exporting CSV files.
Watch out
anything older than one hundred eighty days is out of reach, so save the figures in a sheet if you want a trend over a longer period.
Mailchimp31

List List Members' Activities

Search

In MakeGet the last 50 events of a member's activity on a specific list.

Shows what one contact did lately on an audience, such as opens and clicks: their last fifty events, not their whole history.

When to use it
before a sales call, the rep's CRM record should show what the lead recently did in your emails.
Watch out
you get fifty events at most. For a very active contact, that may cover only a short stretch of their history.

Member Tag

2 modules
Mailchimp32

List Member Tags

Search

In MakeRetireves a list of all member tags

Shows every tag attached to one contact, each as a separate bundle.

When to use it
your support tool should display which tags a customer carries when they open a ticket.
Watch out
a contact with no tag returns nothing, so the next modules won't run for them.
Mailchimp33

Add/Remove Member Tags

Action

In MakeAdds or removes tags from a list member.

Puts tags on a contact or takes them off, in the same module.

When to use it
a trial user becomes a paying customer, so "trial" goes away and "customer" is added.
Watch out
type tag names the same way in every scenario, or you will end up sorting contacts under two labels that mean one thing.

Events

2 modules
Mailchimp34

Add an Event

Action

In MakeAdds a new event to the member.

Records a custom event on a contact, like "downloaded the guide" or "booked a demo", which Mailchimp can then use.

When to use it
someone completes an onboarding step in your app and you want that milestone visible on their Mailchimp profile.
Watch out
keep event names consistent across scenarios, or reports will split the same action in two.
Mailchimp35

Search Member Events

SearchIn the docs only

Looks up the custom events stored on a contact and returns them as bundles.

When to use it
a scenario checks whether a lead has already booked a demo before sending a reminder.
Watch out
Make's docs list this module without describing it; try it with Run once on a test contact to see what it returns.

Survey Answers

1 module
Mailchimp36

List Survey Answers

SearchIn the docs only

Pulls the answers people gave to a Mailchimp survey so you can use them outside Mailchimp.

When to use it
after a product feedback survey, the answers should land in a sheet your product team reviews.
Watch out
the module has no official description; run it once and read its output before building on it.

Reports

2 modules
Mailchimp37

Get a Click Report

Action

In MakeRetrives an existing click report.

Reads the click data of one specific link inside a campaign.

When to use it
you want to know how many readers clicked the "book a call" button in your latest email.
Watch out
you need to know which link you are after; List Click Reports gives you the full set first.
Mailchimp38

List Click Reports

Search

In MakeLists all click reports.

Returns click results for all the links of a campaign, one bundle per link.

When to use it
a post-campaign recap should rank which links drew the most clicks.
Watch out
a long newsletter with many links produces many bundles; aggregate them before writing to a sheet.

Other

1 module
Mailchimp39

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Reaches any part of the Mailchimp API that the other modules don't cover, using the connection you already set up.

When to use it
you need a Mailchimp feature with no dedicated module and don't want to manage keys separately.
Watch out
you write the request yourself, so keep the Mailchimp API reference open; if that feels like too much, Make training covers it.
Need help

Need help automating Mailchimp with Make?

A person reads every message.

FAQ

Mailchimp and Make: common questions

01Is the Mailchimp Make integration free?
Yes, Mailchimp is a standard app in Make, so you can use it on the Free plan. That plan has limits you will feel quickly: 2 active scenarios, at least 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 remove the cap on active scenarios. Make counts usage in operations, one per module per bundle, so busy audiences use more of your monthly allowance.
02What do you need to connect Mailchimp to Make?
Just a Mailchimp account and a Make account. Add any Mailchimp module, click Create a connection, give it a name if you like, save, then log in to Mailchimp and confirm access when asked. Advanced settings are only for people who registered their own Mailchimp app: there you paste its client credentials and use the redirect URI given in the Make docs. Everyone else can skip that part. Once saved, the same connection serves every Mailchimp module in your scenarios.
03Do Mailchimp triggers in Make fire in real time?
Only one does. Watch List Events is instant: Mailchimp calls Make through a webhook as soon as a chosen event happens on the audience. The six others (Watch Campaigns, Watch Subscribers, Watch Unsubscribes, Watch Lists, Watch List Segments and Watch Files) are scheduled, meaning Make checks Mailchimp on the scenario's schedule. A new scenario checks every 15 minutes by default; paid plans allow a tighter interval, down to 1 minute.
04What if the Mailchimp module you need is missing in Make?
Use Make an API Call. It sends any request to the Mailchimp API through the connection you already have, so you can reach features the 46 listed modules leave out. You will need to read the Mailchimp API reference to shape the request. The Make documentation for Mailchimp gives no specific numeric limit, so if a run hits a wall, check your Make plan first: execution time and file size depend on it.
05Should you use Make or n8n for Mailchimp?
It depends on how you like to work. Make gives you a visual editor, a ready connection and 46 Mailchimp modules, which suits teams who want to click together a scenario and see bundles flow. n8n also has a Mailchimp node and suits people who already build their automations there. Start from the modules you actually need and try the one that fits your team's habits. On the Make side, Mailchimp is a standard app, so you can test it on the Free plan before deciding.