Resources · Make integration

Constant Contact Make integrationAutomate Constant Contact with Make.

Can Make keep your Constant Contact lists and campaigns moving on their own? Yes: the Constant Contact Make integration offers 46 modules, including 11 triggers, 19 actions and 16 searches. This guide walks a marketer through the connection, a first scenario and every module.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Constant Contact Make integration do?

The Constant Contact Make integration links your Constant Contact account to Make, a no-code tool where you build a scenario (the automation itself: a chain of modules that runs on a schedule). Each module is one brick: it watches your contacts or email reports, creates or updates records, or looks them up. You set it up once, and the scenario keeps working after you close the tab.

Signups land in the right list. A form or a spreadsheet in another app feeds Create a Contact, and the new person sits in your audience before anyone copies a row by hand. When a whole file arrives, Import Contacts by CSV takes it in one pass, keeping in mind that only the first 4 MB of a larger file are imported.

Campaign results reach the people who need them. Watch Email Clicks Reports or Watch Email Opens Reports picks up new report entries, and the next module forwards them to a sales tool or a shared sheet. Sales sees who clicked without logging in to Constant Contact.

Campaign drafts get a safety check. Watch Email Campaigns spots a new campaign, and Test an Email Campaign Activity sends a test version so someone proofreads it first. Constant Contact caps those test sends at 50 per day.

What Make does not do here: every trigger of this app is scheduled, so Make checks Constant Contact at intervals and nothing arrives the instant it happens. When a listed module does not cover your need, Make an API Call reaches the rest of the API with the same connection. Constant Contact often has an n8n node too; the n8n vs Make comparison helps you choose, and the Make review covers the tool itself. If you would rather hand the build over, see the Make agency page.

Connect

How do you connect Constant Contact to Make?

  1. 01

    Add a Constant Contact module

    Log in to Make, open your scenario and add any Constant Contact module. In the module panel, click Create a connection. A connection is your Constant Contact account linked to Make once and then reused by every Constant Contact module you add later.

  2. 02

    Name the connection

    The Connection name field is optional, but a clear label pays off the day you manage two accounts. Something like the brand or the client name works, so a teammate picks the right account from the dropdown without guessing.

  3. 03

    Authorize with your credentials

    Enter the credentials copied from your Constant Contact account, or follow the instructions Make shows on screen. For the advanced setup, register an application in My Applications, paste the callback URI Make expects, then copy the Client ID and the Client secret into Make.

First scenario

Your first scenario: add form signups to Constant Contact

GoalWhen someone fills in a form in another app, Make creates that person as a contact in Constant Contact.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. The first module you pick decides when the scenario starts, so choose the app where your signups come in.

  2. 02

    Set up the form trigger

    Search for your form or spreadsheet app, pick the module that watches new entries and create its connection. Make then lists the forms or sheets it can read, so you pick yours from a menu.

  3. 03

    Add Create a Contact

    Click the + on the right of the first module, search for Constant Contact and choose Create a Contact. Connect your account, then map the details captured by the form into the fields Make shows.

  4. 04

    Test with Run once

    Submit a test entry in your form, then click Run once. Each module shows the bundles it received (a bundle is one item passing through, here one signup). Open Constant Contact and check the new contact.

  5. 05

    Schedule and switch it on

    Open the clock on the first module. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan. Then switch the scenario on and let it work.

Triggers

What can start a Constant Contact scenario?

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

Constant Contact1Watch Contact Activities

Watch Contact Activities

Scheduled trigger

In MakeTriggers by new activities of a contact for specific events.

Your scenario gets a fresh bundle each time a contact logs new activity on the events you pick, so follow-up happens without anyone reading reports. It is the trigger for acting on what one person did.

How it fires
scheduled, Make checks Constant Contact on the scenario's schedule and collects the activities logged since the previous check.
When to use it
a contact engages with a campaign and your sales tool should record it on the matching lead.
Watch out
each activity becomes one bundle, and every module after it spends an operation per bundle, so a busy audience adds up quickly.
Constant Contact2Watch Contacts

Watch Contacts

Scheduled trigger

In MakeTriggers by contact create or update events. Optionally filters by contact status.

New or edited contacts flow straight into the rest of your stack with this trigger, which picks up both creations and updates. You can narrow it to a contact status when only some people matter.

How it fires
scheduled, Make looks at Constant Contact at each run of the scenario, every 15 minutes by default.
When to use it
your CRM or a shared sheet should mirror the audience that marketing edits in Constant Contact.
Watch out
since updates also fire it, avoid pairing it with Update a Contact on the same account, or the scenario feeds itself.
Constant Contact3Watch Email Bounces Reports

Watch Email Bounces Reports

Scheduled trigger

In MakeTriggers by new email bounces reports.

Bounced addresses become visible outside Constant Contact once this trigger catches new entries in the bounces report. Someone can then fix a typo or call the client instead of losing the address.

How it fires
scheduled, the report is read on the scenario's schedule, never the moment the bounce happens.
When to use it
account managers want a task or a message whenever one of their customers stops receiving emails.
Watch out
a large send can produce many bounces at once, and each one is a bundle that costs operations in the modules downstream.
Constant Contact4Watch Email Campaigns

Watch Email Campaigns

Scheduled trigger

In MakeTriggers by new email campaigns.

Every new email campaign created in Constant Contact starts the scenario, which gives your team a hook for review, logging or announcements. It watches campaigns, not their results.

How it fires
scheduled, Make asks Constant Contact for new campaigns at each run, with the default schedule set at 15 minutes.
When to use it
you keep a campaign calendar in another tool and want each new campaign listed there without retyping it.
Watch out
every new campaign counts, test drafts included, so add a filter after the trigger if only some campaigns should go through.
Constant Contact5Watch Email Clicks Reports

Watch Email Clicks Reports

Scheduled trigger

In MakeTriggers by new email clicks reports.

Clicks are the clearest sign of interest, and this trigger hands each new click report entry to your scenario. Sales can call a warm contact while the email is still fresh in their mind.

How it fires
scheduled, Make reads the clicks report on the scenario's schedule and passes along what is new.
When to use it
a click on a pricing or demo link should create a follow-up task in the tool your sales team lives in.
Watch out
the Free plan checks every 15 minutes at best; if sales needs the click sooner, paid plans go down to 1 minute.
Constant Contact6Watch Email Did Not Opens Reports

Watch Email Did Not Opens Reports

Scheduled trigger

In MakeTriggers by new email did not opens reports.

People who ignored a campaign are worth a second try, and this trigger surfaces them from the did not opens report. It turns silence into a list you can act on.

How it fires
scheduled, Make pulls new report entries at each run of the scenario.
When to use it
a key announcement went out and your account managers should reach the customers who never opened it by phone or another channel.
Watch out
every contact in the report becomes a bundle; add a filter after the trigger so later modules only handle the contacts that matter.
Constant Contact7Watch Email Forwards Reports

Watch Email Forwards Reports

Scheduled trigger

In MakeTriggers by new email forwards reports.

A forward means someone shared your email with a colleague, and this trigger catches every new forward entry so you can thank or qualify that contact. It is a quiet referral signal most teams never look at.

How it fires
scheduled, Constant Contact is checked on the scenario's schedule for fresh forward entries.
When to use it
a B2B newsletter forwarded inside a company hints at a buying group worth flagging in your CRM.
Watch out
Run once returns nothing until a real forward exists, so test it after someone has actually forwarded a campaign.
Constant Contact8Watch Email Opens Reports

Watch Email Opens Reports

Scheduled trigger

In MakeTriggers by new email opens reports.

Open events reach the rest of your tools through this trigger, which picks up each new entry in the opens report. Use it when every open counts, including repeat opens.

How it fires
scheduled, Make reads the opens report whenever the scenario runs, not at the moment of the open.
When to use it
you score engagement in a CRM and each open should add to a contact's score.
Watch out
one person opening an email several times can mean several bundles; pick Watch Email Unique Opens Reports if you only need each reader once.
Constant Contact9Watch Email Opt-outs Reports

Watch Email Opt-outs Reports

Scheduled trigger

In MakeTriggers by new email opt-outs reports.

Unsubscribes need to travel beyond Constant Contact, and this trigger sends each new opt-out entry to your scenario. Other tools can then stop messaging that person too.

How it fires
scheduled, Make checks the opt-outs report at every run of the scenario.
When to use it
your CRM or support tool also sends emails, and the opt-out flag should be copied there so nobody writes to that contact by mistake.
Watch out
the copy happens at the next scheduled run, so keep the interval short on a scenario that handles consent.
Constant Contact10Watch Email Sends Reports

Watch Email Sends Reports

Scheduled trigger

In MakeTriggers by new email sends reports.

This trigger confirms who actually received a campaign by passing each new sends report entry to Make. You get a delivery log outside Constant Contact without exporting anything.

How it fires
scheduled, the sends report is polled on the scenario's schedule.
When to use it
a compliance or client reporting sheet must list every recipient of a given campaign.
Watch out
a send to a large list creates one bundle per recipient, so check your operations before you point it at a full audience.
Constant Contact11Watch Email Unique Opens Reports

Watch Email Unique Opens Reports

Scheduled trigger

In MakeTriggers by new email unique opens reports.

Counting readers rather than opens is what this trigger is for: it reports each new unique open, one per person. Your follow-up then fires once per reader, not every time they reopen.

How it fires
scheduled, Make fetches new unique opens whenever the scenario runs, every 15 minutes unless you change it.
When to use it
a thank-you or next-step email from another tool should go out once to each person who opened.
Watch out
do not stack it with Watch Email Opens Reports in the same flow, or readers get counted twice.
Modules

What can Make do in Constant Contact?

Constant Contact gives you 35 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Constant Contact1

Create a Contact

Action

In MakeCreates a new contact.

Adds one new person to your Constant Contact audience from data that arrives in the scenario, such as a form entry or a new customer in your shop.

When to use it
one signup at a time, right after the module that captured it.
Watch out
for a batch of people, Import Contacts saves you one operation per contact.
Constant Contact2

Create a Contact List

Action

In MakeCreates a new contact list.

Opens a new list in Constant Contact so a fresh segment has a home before contacts go into it.

When to use it
a webinar or an event is created in another tool and its attendees need their own list.
Watch out
run it once per segment, not once per contact, or you end up with a pile of near duplicate lists.
Constant Contact3

Create an Email Campaign

Action

In MakeCreates a new email campaign.

Drafts a new email campaign in Constant Contact from content prepared elsewhere, so your writers keep working in their usual tool.

When to use it
a blog post or product note is approved and a matching campaign draft should appear for the marketing team.
Watch out
the send itself belongs to Schedule an Email Campaign Activity, so keep a review step between the two.
Constant Contact4

Delete a Contact

Action

In MakeRemoves a contact by its ID. Deleted contacts can be revived.

Removes a contact from Constant Contact using its ID, typically after a request that comes in through another tool.

When to use it
a customer asks to be erased and your support desk records that request.
Watch out
Constant Contact can revive deleted contacts, so a deletion is not the same as a permanent erasure; get the ID from a search first.
Constant Contact5

Delete a Contact List

Action

In MakeRemoves a contact list by its ID.

Removes an entire list by its ID, which keeps your list picker readable once a segment has served its purpose.

When to use it
an event is closed in your project tool and its temporary list should go too.
Watch out
place List Contact Lists before it and check the ID in a Run once test, because the wrong ID removes the wrong list.
Constant Contact6

Delete an Email Campaign

Action

In MakeRemoves an email campaign by its ID.

Removes an email campaign by its ID, handy for clearing test drafts that a scenario created earlier.

When to use it
a draft built by Create an Email Campaign was rejected during review in another tool.
Watch out
treat it as final and keep it behind a filter, so only campaigns marked as rejected ever reach this module.
Constant Contact7

Delete Contacts from Lists

Action

In MakeRemoves contacts from lists by their IDs.

Takes contacts out of lists using their IDs, which keeps each segment accurate when someone changes status in another tool.

When to use it
a lead becomes a customer in your CRM and should leave the prospect list without losing their history.
Watch out
this module needs IDs, not email addresses, so look the contacts up with List Contacts first.
Constant Contact8

Get an Email Campaign

Action

In MakeRetrieves details of an email campaign by its ID.

Fetches the details of one email campaign by its ID so later modules can reuse them, for example in a report or a message to your team.

When to use it
Watch Email Campaigns returned a new campaign and you want its full details before posting it somewhere.
Watch out
it returns one campaign; use List Email Campaigns to browse several.
Constant Contact9

Get an Email Campaign Activity

Action

In MakeRetrieves details of an email campaign activity by its ID.

Reads one campaign activity by its ID. Most activity modules and every report module expect that ID, so this is where you confirm you hold the right one.

When to use it
you want to check an activity's details before testing, scheduling or reporting on it.
Watch out
a campaign ID and an activity ID are different things; map the one the next module asks for.
Constant Contact10

Import Contacts

Action

In MakeImports contacts by an array of contacts. Existing contact with the same email will be replaced.

Sends a batch of contacts to Constant Contact in one step, straight from data already in the scenario, instead of creating them one by one.

When to use it
an aggregator has gathered several new customers from your shop and you push them together.
Watch out
an existing contact with the same email gets replaced, so make sure the incoming data is complete before you import.
Constant Contact11

Import Contacts by CSV

Action

In MakeImports contacts by a CSV file. Only the first 4 MB of the file will be imported if the file exceeds 4 MB.

Loads contacts from a CSV file, which suits exports from a trade show scanner, a partner or an old tool.

When to use it
a CSV lands in a shared folder and should reach Constant Contact without anyone opening it.
Watch out
only the first 4 MB of a larger file get imported, so split big files before they reach this module.
Constant Contact12

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Reaches any endpoint of the Constant Contact API with the connection you already set up, for the jobs the other modules do not cover.

When to use it
you need an operation of the API that has no dedicated module in Make.
Watch out
you write the request yourself, so keep the Constant Contact API documentation open and start with a Run once test.
Constant Contact13

Preview an Email Campaign Activity

Action

In MakePreviews an email campaign activity by its ID.

Returns a preview of a campaign activity by its ID, so a reviewer can see the email without opening Constant Contact.

When to use it
a new draft should be posted to a review channel where your manager signs off on it.
Watch out
a preview is not a real send; use Test an Email Campaign Activity to see the email in an inbox.
Constant Contact14

Schedule an Email Campaign Activity

Action

In MakeSchedules an email campaign activity by its ID.

Plans the send of a campaign activity by its ID, which lets an approval in another tool trigger the actual release.

When to use it
the campaign is approved in your project tool and should go out without someone logging in to click send.
Watch out
put a test and a review step before it, because once scheduled the email leaves for real.
Constant Contact15

Summarize Average Open and Click Rates

Action

In MakeSummarizes average open and click rates by the contact ID.

Gives the average open and click rates of one contact, identified by ID, so you can judge how engaged that person is.

When to use it
a lead is about to be passed to sales and your CRM should show how that contact reacts to your emails.
Watch out
it works per contact, so each person you summarize costs one operation.
Constant Contact16

Test an Email Campaign Activity

Action

In MakeTests an email campaign activity by its ID with a daily limit of 50 test emails.

Sends a test version of a campaign activity by its ID, so a real person checks the email in a real inbox before release.

When to use it
a draft appears and your proofreader should receive it straight away.
Watch out
Constant Contact allows 50 test emails per day, so avoid running this inside a loop over many contacts.
Constant Contact17

Unschedule an Email Campaign Activity

Action

In MakeUnschedules an email campaign activity by its ID.

Cancels the planned send of a campaign activity by its ID, which is your safety net when something changes at the last minute.

When to use it
a product is pulled or an offer changes in another tool, and the related campaign must not go out.
Watch out
map the activity ID, not the campaign ID, and test it on a dummy campaign before trusting it with a live send.
Constant Contact18

Update a Contact

Action

In MakeUpdates a contact by its ID.

Changes an existing contact by its ID, so details edited in your CRM or shop also land in Constant Contact.

When to use it
a customer corrects their details in your billing tool and marketing should work from the same version.
Watch out
if Watch Contacts starts the same scenario, each update can fire it again; watch the other app instead.
Constant Contact19

Update a Contact List

Action

In MakeUpdates a contact list by its ID.

Edits an existing list by its ID, for instance to rename it when a segment changes purpose.

When to use it
an event gets renamed in your planning tool and the matching list should follow.
Watch out
retrieve the ID with List Contact Lists first, since list names alone are not enough for this module.
Constant Contact20

Get an Email Campaign Activity Send History

Search

In MakeRetrieves the send history of an email campaign activity by its ID.

Returns the send history of one campaign activity, so you know when and how often it actually went out.

When to use it
a client report should show every send of a recurring newsletter activity.
Watch out
as a search, it can return zero, one or several bundles; add an aggregator if you want a single summary line.
Constant Contact21

Get Email Bounces Reports

Search

In MakeRetrieves email bounces reports by the email campaign activity ID.

Pulls the bounces of a given campaign activity on demand, so a cleanup can happen right after a send.

When to use it
a scenario started by another event needs the bounce list of one specific campaign.
Watch out
it needs the activity ID, not the campaign ID; the trigger version, Watch Email Bounces Reports, suits ongoing monitoring better.
Constant Contact22

Get Email Clicks Reports

Search

In MakeRetrieves email clicks reports by the email campaign activity ID.

Lists who clicked in one campaign activity, which gives sales a ready call list from a single send.

When to use it
after a product launch email, you want every clicker added to a follow-up sheet in one go.
Watch out
each clicker comes back as a separate bundle, and every module after it spends one operation per bundle.
Constant Contact23

Get Email Did Not Opens Reports

Search

In MakeRetrieves email did not opens reports by the email campaign activity ID.

Gathers the recipients of one campaign activity who never opened it, so you can plan another touchpoint for them.

When to use it
an event reminder was ignored by some guests and your team wants to text or call them.
Watch out
every silent recipient is a bundle, so filter the list down before modules that cost operations.
Constant Contact24

Get Email Forwards Reports

Search

In MakeRetrieves email forwards reports by the email campaign activity ID.

Shows which recipients forwarded one campaign activity, a hint of who spreads your content inside their company.

When to use it
you want to tag those forwarders in your CRM after an important B2B mailing.
Watch out
the search can come back empty; plan the next step so the rest of the scenario handles a result with no bundle.
Constant Contact25

Get Email Links Reports

Search

In MakeRetrieves email links reports by the email campaign activity ID.

Breaks down the clicks of one campaign activity by link, so you learn which call to action actually worked.

When to use it
your content team keeps a results sheet and wants link performance logged per campaign.
Watch out
this report is about links, not people; use Get Email Clicks Reports when you need the contacts behind the clicks.
Constant Contact26

Get Email Opens Reports

Search

In MakeRetrieves email opens reports by the email campaign activity ID.

Retrieves the opens of one campaign activity, repeats included, for a full picture of how the email was read.

When to use it
an engagement dashboard counts every open, not just readers.
Watch out
the same person may appear several times; switch to Get Email Unique Opens Reports to get each reader once.
Constant Contact27

Get Email Opt-outs Reports

Search

In MakeRetrieves email opt-outs reports by the email campaign activity ID.

Lists the people who unsubscribed after one campaign activity, which helps you spot a message that pushed readers away.

When to use it
you review each campaign and want its opt-outs copied to your CRM as well.
Watch out
it reads one activity at a time; for continuous syncing, Watch Email Opt-outs Reports is the better start.
Constant Contact28

Get Email Sends Reports

Search

In MakeRetrieves email sends reports by the email campaign activity ID.

Returns every recipient of one campaign activity, a clean delivery list for audits or client reporting.

When to use it
an agency needs to prove to a client which addresses a campaign reached.
Watch out
expect as many bundles as recipients; an aggregator can fold them into one file or one row.
Constant Contact29

Get Email Unique Opens Reports

Search

In MakeRetrieves email unique opens reports by the email campaign activity ID.

Returns each person who opened one campaign activity, counted once, which is the fairest measure of reach.

When to use it
you send a single follow-up to every reader of a launch email.
Watch out
like other reports here, it wants the activity ID; Get an Email Campaign Activity helps you confirm it.
Constant Contact30

List Contact Action Summaries

Search

In MakeLists action summary for a contact in email campaign activities by the contact ID.

Summarizes what one contact did across your campaign activities, so a salesperson gets a quick read before a call.

When to use it
a meeting is booked with a lead and your CRM should show their email engagement.
Watch out
it needs the contact ID; find it with List Contacts if your data only holds an email address.
Constant Contact31

List Contact Activities

Search

In MakeLists contact activities by its ID.

Pulls the activity history of one contact on demand, rather than waiting for a trigger to catch new events.

When to use it
a support ticket opens and the agent should see how that customer interacted with your emails.
Watch out
a long history means many bundles; filter it or aggregate it before sending it anywhere.
Constant Contact32

List Contact Lists

Search

In MakeRetrieves a list of contact lists.

Retrieves your contact lists, which is how the scenario finds the ID of the list it needs to work with.

When to use it
before Update a Contact List, Delete a Contact List or any step that takes a list ID.
Watch out
it returns every list as a separate bundle; add a filter on the name to keep only the one you want.
Constant Contact33

List Contacts

Search

In MakeRetrieves a list of contacts and filtered by criteria.

Finds contacts that match your criteria, the usual way to turn an email address into the contact ID other modules require.

When to use it
ahead of Update a Contact or Delete a Contact, when your data only holds an email.
Watch out
a loose filter can return many bundles, so narrow the criteria and test with Run once.
Constant Contact34

List Email Campaign Activity Schedules

Search

In MakeRetrieves a list of schedules of an email campaign activity by its ID.

Shows the planned sends of one campaign activity, a quick way to confirm when an email is set to go out.

When to use it
your team wants upcoming sends posted to a chat channel whenever a campaign is approved.
Watch out
an unscheduled activity simply returns nothing, so plan the next step for an empty result.
Constant Contact35

List Email Campaigns

Search

In MakeRetrieves a list of email campaigns.

Retrieves your email campaigns so a scenario can report on them, archive them or pick one by name.

When to use it
a management review needs the list of campaigns copied into a spreadsheet.
Watch out
each campaign is its own bundle; filter before costly modules to protect your operations.
Need help

Need help automating Constant Contact with Make?

A person reads every message.

FAQ

Constant Contact and Make: common questions

01Is the Constant Contact Make integration free?
Yes, on the Make side. Constant Contact is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum interval of 15 minutes between scheduled runs, runs of up to 5 minutes, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. Usage is counted in operations each month. You still need your own Constant Contact subscription.
02What do you need to connect Constant Contact to Make?
You need a Constant Contact developer account and a registered application, which gives you the API key Make uses. In Make, add any Constant Contact module, click Create a connection, optionally name it, and enter the credentials from your account. For the advanced route, the application you register in Constant Contact must use the callback URI given by Make, and you copy its Client ID and Client secret into the connection. Once saved, every Constant Contact module reuses that same connection.
03Do Constant Contact triggers in Make fire in real time?
No. All 11 Constant Contact triggers in Make are scheduled, none are instant. Make checks Constant Contact at each run of the scenario, every 15 minutes by default, and picks up what changed since the last check. On a paid plan you can shorten the interval to 1 minute, which gets close without being immediate. If an event must reach Make the second it happens, this app does not offer that through its listed triggers.
04What if a Constant Contact module is missing in Make?
Use Make an API Call. It sends any request to the Constant Contact API with the connection you already have, so an operation without a dedicated module is still within reach. You write the request yourself, so keep the Constant Contact API documentation at hand and test with Run once. Also keep the known limits in mind: Import Contacts by CSV reads only the first 4 MB of a file, and test sends stop at 50 per day.
05Should you use Make or n8n for Constant Contact?
It depends on what you need to automate. In Make, Constant Contact comes with 46 modules: 11 scheduled triggers, 19 actions and 16 searches, plus Make an API Call for the rest of the API. Constant Contact often has an n8n node as well. List the modules your scenario requires and check that each tool covers them, including the API call route. The n8n vs Make comparison linked above lays out the criteria side by side, without declaring a winner.