Resources · Make integration

Campaign Monitor Make integrationAutomate Campaign Monitor with Make.

New subscriber on a list? Make can greet them for you. The Campaign Monitor Make integration gives you 10 modules: 1 instant trigger, 7 actions and 2 searches. This guide is for marketers who know Campaign Monitor, and it walks you from connecting your account to a live first scenario.

Try the Campaign Monitor integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Campaign Monitor Make integration do?

The Campaign Monitor Make integration links your Campaign Monitor account to Make so your lists and emails react to what happens elsewhere, with no code. You build a scenario, the automation itself, out of modules: small bricks that each watch, read or change one thing in Campaign Monitor.

Welcome every new subscriber. Watch Subscribers fires the moment someone joins a list you picked, and Send a Smart Email delivers the Smart Email template you designed in Campaign Monitor. Nobody has to export a list by hand.

Keep subscriber records in step with your CRM. When a deal changes stage in another tool, Get a Subscriber checks who is on file, then Update a Subscriber or Add a Subscriber writes the change. If a customer asks to stop hearing from you, Unsubscribe a Subscriber takes them off the list without a manual export.

Share campaign results with the team. Get a Campaign Summary pulls the basic results of a sent campaign so Make can post them in a chat channel or a spreadsheet.

Everything beyond these 10 modules goes through Make an API Call, which reaches any endpoint of the Campaign Monitor API with the same connection. New to the platform? The Make review covers the basics, and the Make pricing page explains how operations are counted. Campaign Monitor may also have an n8n node; the n8n vs Make comparison helps you pick.

Connect

How do you connect Campaign Monitor to Make?

  1. 01

    Add a Campaign Monitor module

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

  2. 02

    Name the connection

    The Connection name field is optional, but a clear label such as the client or brand helps when you manage several Campaign Monitor accounts from the same Make workspace.

  3. 03

    Paste your credentials

    Enter the API key you copied from Campaign Monitor, or follow the on-screen instructions to create the connection. You need an active Campaign Monitor account and either an API key or a registered OAuth application before you start.

First scenario

Build your first scenario: welcome new subscribers

GoalWhen someone joins a list in Campaign Monitor, Make sends them your welcome Smart Email.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + to add the first module. Search for Campaign Monitor and choose Watch Subscribers.

  2. 02

    Create the webhook and pick your list

    Click Create a webhook, then Create a connection if you have none yet. Once connected, Make shows the lists it can read; select the one your signup form feeds.

  3. 03

    Add the welcome email

    Click the + on the right of the trigger and add Send a Smart Email. Choose your template, then map the new subscriber's details from the previous module so each message goes to the right person.

  4. 04

    Test with Run once

    Click Run once, then add a test address to the list. Each module shows the bundles it received: a bundle is one item passing between modules, here one subscriber.

  5. 05

    Switch it on

    When the test looks right, turn the scenario on. From then on Campaign Monitor calls Make for every new subscriber, and each module run counts as one operation on your plan.

Triggers

What starts a Campaign Monitor scenario

1 module starts a scenario when something happens in Campaign Monitor. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Campaign Monitor as soon as it happens.

Campaign Monitor1Watch Subscribers

Watch Subscribers

Instant trigger

In Make“Watches for new subscribers in a selected list.”

This trigger hands your scenario every person who joins a list you choose, so follow-up work starts without anyone checking the list. It is the only trigger in the app, which makes it the natural entry point for onboarding flows.

How it fires
instant. Campaign Monitor calls Make through a webhook as soon as the subscriber is added, instead of Make checking on a schedule.
When to use it
a newsletter signup that should get a welcome email, a CRM record or a note to sales.
Watch out
it reports new subscribers on the list you selected, not changes to people already on it, so pair it with other modules for updates.
Modules

What each Campaign Monitor module does

Campaign Monitor gives you 9 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Campaign Monitor1

Add a Subscriber

Action

In Make“Creates a new subscriber.”

Puts a new person on a Campaign Monitor list from any source Make can read, so leads from forms, shops or events land in your audience automatically.

When to use it
a buyer checks the marketing box at checkout and should join your customer list.
Watch out
if the person may already exist, run Get a Subscriber first so you choose between adding and updating.
Campaign Monitor2

Delete a Webhook

Action

In Make“Deletes a webhook.”

Removes a webhook from your Campaign Monitor account, which keeps old notifications from reaching scenarios you no longer use.

When to use it
cleaning up after you retire a scenario that relied on Watch Subscribers.
Watch out
first make sure no active scenario still relies on it, since a scenario that listens to a removed webhook has nothing left to receive.
Campaign Monitor3

Get a Campaign Summary

Action

In Make“Gets a basic summary of the results for a specific sent campaign.”

Fetches a basic summary of the results of one campaign you already sent, ready to be pasted into a report or a message to the team.

When to use it
posting the outcome of a launch email in your team chat once it has gone out.
Watch out
it works on sent campaigns only; a draft has no results to summarize.
Campaign Monitor4

Get a Subscriber

Action

In Make“Gets subscriber's details.”

Reads the details of one subscriber, so the rest of the scenario can decide what to do based on what Campaign Monitor already knows about that person.

When to use it
before adding a contact from your CRM, to check whether they are already on the list.
Watch out
it looks up a single subscriber; plan a branch for the case where nobody is found.
Campaign Monitor5

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Covers whatever the nine other modules leave out: it calls any endpoint of the Campaign Monitor API, reusing the connection you already created.

When to use it
you need a Campaign Monitor feature that has no dedicated module in Make.
Watch out
you write the request yourself, so keep the Campaign Monitor API documentation open while you set it up.
Campaign Monitor6

Unsubscribe a Subscriber

Action

In Make“Unsubscribes from a list.”

Takes a person off a list the moment another tool says they want out, so your sends respect their choice without a manual export.

When to use it
a customer closes their account in your app or asks support to stop the emails.
Watch out
it acts on one list; someone on several lists needs one run per list.
Campaign Monitor7

Update a Subscriber

Action

In Make“Updates subscribers details.”

Changes the details of someone already on your list, which keeps segments and personalization accurate as your other tools learn more about them.

When to use it
a lead becomes a customer in your CRM and the list record should reflect it.
Watch out
it needs an existing subscriber; for a new address use Add a Subscriber instead.
Campaign Monitor8

Send a Regular Email

Search

In Make“Sends a regular email.”

Sends a regular email through Campaign Monitor from inside a scenario, so a message can go out as a direct reaction to an event in another app.

When to use it
a plain announcement where you would rather not maintain a Smart Email template.
Watch out
Make lists it as a search module, so read what it returns during Run once before mapping its output.
Campaign Monitor9

Send a Smart Email

Search

In Make“Sends a smart email.”

Sends one of the Smart Email templates you designed in Campaign Monitor, filled with data mapped from earlier modules, so branded messages stay consistent.

When to use it
welcome, receipt or password messages that reuse the same layout for every recipient.
Watch out
like Send a Regular Email, it is filed as a search, so check its bundles with Run once first.
Need help

Need help automating Campaign Monitor with Make?

A person reads every message.

FAQ

Campaign Monitor and Make: frequent questions

01Is the Campaign Monitor Make integration free?
Yes, Campaign Monitor is a standard app, so all 10 modules work on the Make Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Each module run is one operation, which is what Make counts against your plan. You still need your own Campaign Monitor subscription.
02What do you need to connect Campaign Monitor to Make?
An active Campaign Monitor account plus either an API key or a registered OAuth application. In Make, add a Campaign Monitor module, click Create a connection, give it a name if you like and paste the credentials. For OAuth, open Integrations in Campaign Monitor, choose a client if asked, click OAuth Registration, enter the callback URI given by Make and copy the Client ID and Client secret it displays. For the instant trigger, click Create a webhook before creating the connection.
03Does the Campaign Monitor trigger in Make fire in real time?
Yes. Watch Subscribers is an instant trigger: Campaign Monitor calls Make through a webhook as soon as someone joins the selected list, so your scenario does not wait for a scheduled check. That is why the module shows a lightning badge in the editor rather than a clock. Scheduled triggers, by contrast, are polled on the scenario's schedule, every 15 minutes by default. Test it with Run once and a test address before switching the scenario on.
04What if a Campaign Monitor module is missing in Make?
Use Make an API Call. It sends any request to the Campaign Monitor API with the connection you already set up, so features without a dedicated module are still reachable. You write the request yourself, using the Campaign Monitor API documentation as your guide. Make also notes that its Campaign Monitor documentation is AI-generated from the vendor's docs and may contain mistakes, so confirm important details with Campaign Monitor directly.
05Should you use Make or n8n for Campaign Monitor?
It depends on where the rest of your automations already live. On Make, Campaign Monitor offers 10 modules, including an instant trigger for new subscribers and Make an API Call for anything else, and it runs on the Free plan. The same app may have an n8n node too, so compare what each side offers for your exact use case before deciding. If your team already builds scenarios in Make, keeping Campaign Monitor there avoids splitting your workflows across two tools.
Same platform

Other docs you might need on this stack.

Browse all integrations