Resources · Make integration

EmailOctopus Make integrationAutomate EmailOctopus with Make.

Your subscribers can move between tools without a single export. The EmailOctopus Make integration gives you 17 modules: 3 triggers, 11 actions and 3 searches. This guide connects your API key and walks you through a first working scenario.

Try the EmailOctopus integration on MakeSee the 17 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the EmailOctopus Make integration do?

The EmailOctopus Make integration links your newsletter account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a single brick such as a trigger, an action or a search. Make watches your campaigns, contacts and lists, then adds, updates or reads subscribers for you.

Grow a list from other tools. Put Create a Contact in a List after a form, a CRM or a spreadsheet module, and every new lead lands in the right EmailOctopus list without a CSV import.

Keep two audiences in step. Watch Contacts spots each new subscriber, and Update a Contact in a List or Delete a Contact from a List keeps a second list or another tool aligned. If Airtable is where your data lives, the Airtable Make integration pairs well here.

Share campaign results. Watch Campaigns notices each new campaign, and Get Campaign Report: Summary pulls its figures so you can send them to a sheet or a chat channel.

What Make does not do here: every EmailOctopus trigger is scheduled, so Make checks the account on the scenario's clock instead of reacting the second something happens. For anything outside the 17 modules, Make an API Call reaches the rest of the EmailOctopus API with the same connection.

Still choosing a platform? The n8n vs Make comparison lays out both tools, and the Make pricing page explains what each plan includes.

Connect

How do you connect EmailOctopus to Make?

  1. 01

    Create an API key in EmailOctopus

    You need an active EmailOctopus account and an API key. From your dashboard, open the API key screen, click Add key at the bottom of the page, give the key a name, then click Create and copy the key shown in the window.

  2. 02

    Add an EmailOctopus module in Make

    Log in to Make, open your scenario and add any EmailOctopus module. Click Create a connection. A connection is your EmailOctopus account linked to Make once, and every EmailOctopus module in your scenarios reuses it.

  3. 03

    Paste the key and save

    Type a label in Connection name if you like, which helps when you run several accounts. Then paste the API key you copied and confirm. Make can now list your campaigns, lists and contacts inside each module.

First scenario

Your first scenario with EmailOctopus and Make

GoalWhen a new contact joins an EmailOctopus list, Make adds that person to a second list you pick.

  1. 01

    Start a blank scenario

    Go to the Scenarios page, create a new scenario and click the big + to add the first module. The first module decides when the whole scenario starts.

  2. 02

    Add Watch Contacts

    Search for EmailOctopus, pick Watch Contacts and select your connection. Make lists your EmailOctopus lists, so choose the source list and whether you want subscribed, unsubscribed or any contacts.

  3. 03

    Add Create a Contact in a List

    Click the + on the right of the trigger and add Create a Contact in a List. Pick a different target list, then map the contact data coming from Watch Contacts into the fields.

  4. 04

    Test with Run once

    Add a test subscriber to the source list, then click Run once. Open the bubble above each module to read the bundle it received, which is one contact passing from module to module.

  5. 05

    Schedule and switch it on

    Click the clock on the first module to set the schedule. A new scenario runs every 15 minutes by default. Save, then switch the scenario on so it keeps copying new subscribers.

Triggers

What can start an EmailOctopus scenario?

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

EmailOctopus1Watch Campaigns

Watch Campaigns

Scheduled trigger

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

Each time someone on your team creates a new campaign in EmailOctopus, this trigger hands it to your scenario as a bundle. That gives you a clean starting point for logging campaigns in a planning sheet or telling the rest of the team that a new send is in the works.

How it fires
scheduled, Make checks EmailOctopus on the scenario's schedule and picks up the campaigns created since the last check.
When to use it
you want a shared record of every campaign without asking anyone to fill it in by hand.
Watch out
a campaign that was just created usually has no results yet, so fetch its report in a separate scenario later.
EmailOctopus2Watch Contacts

Watch Contacts

Scheduled trigger

In Make“Triggers when a new contact is added to a list as subscribed or unsubscribed or as any.”

This one reacts to new people in a list. You pick the list and the kind of contact you care about, subscribed, unsubscribed or any, and every match reaches your scenario ready to be copied, tagged or pushed to another tool.

How it fires
scheduled, Make checks the list on the scenario's schedule rather than the moment the person signs up.
When to use it
a new subscriber should also appear in your CRM, or an unsubscribe should be recorded in a sales tool.
Watch out
if the same scenario writes contacts back into the watched list, it will pick them up again on the next run.
EmailOctopus3Watch Lists

Watch Lists

Scheduled trigger

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

Creating a new list in EmailOctopus becomes an event your scenario can act on. The trigger passes along the fresh list so a later module can read it, document it or prepare what should happen around it in your other tools.

How it fires
scheduled, Make looks for lists created since its last check, following the scenario's schedule.
When to use it
your team opens a list per event or per product and you want each one noted in a shared tracker.
Watch out
the trigger only sees new lists; renaming or editing an existing list will not start the scenario.
Modules

What can Make do in EmailOctopus?

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

EmailOctopus1

Create a Contact in a List

Action

In Make“Creates a contact of a list.”

New leads from forms, shops or a CRM end up in the EmailOctopus list you choose, with no CSV import. It is the natural last step when a scenario feeds your audience.

When to use it
a lead fills in a signup form elsewhere and should receive your next newsletter.
Watch out
check your consent rules before adding people who never asked for your emails.
EmailOctopus2

Create a List

Action

In Make“Creates a new list.”

Opens a brand new list in your EmailOctopus account from inside a scenario, so an audience can exist before its first contact arrives.

When to use it
each new webinar, course or client project in another tool needs its own mailing list.
Watch out
run it once per event, otherwise a scenario that fires on every bundle will create duplicate lists.
EmailOctopus3

Delete a Contact from a List

Action

In Make“Deletes a contact of a list.”

Removes one person from a specific list, which keeps your audience clean when that person leaves or asks to stop hearing from you in another tool.

When to use it
a customer closes their account in your app and should disappear from the customer newsletter.
Watch out
a delete cannot be undone from Make, so test on a dummy contact with Run once first.
EmailOctopus4

Delete a List

Action

In Make“Deletes a list.”

Wipes an entire list from EmailOctopus. Pick this over Delete a Contact from a List only when the whole audience has no further use, such as a finished event.

When to use it
cleaning up temporary lists after a project closes in your project tool.
Watch out
a deleted list does not come back, so add a filter that confirms you target the right one.
EmailOctopus5

Get a Campaign

Action

In Make“Gets details of a campaign.”

Fetches the details of one campaign you already know, handy when a previous module gives you its ID and you need the rest of its information to build a message or a record.

When to use it
after Watch Campaigns, to enrich a row in your content calendar.
Watch out
it returns the campaign itself, not its results; use Get Campaign Report: Summary for those.
EmailOctopus6

Get a Contact from a List

Action

In Make“Gets details of a contact of a list.”

Looks up one subscriber in a given list and returns everything EmailOctopus holds about them, so the next module can decide what to do based on that record.

When to use it
before updating someone, to see whether they are still subscribed.
Watch out
it works on a single list; the same person in another list needs a second lookup.
EmailOctopus7

Get a List

Action

In Make“Gets details of a list.​”

Returns the details of one EmailOctopus list, which is useful when a later module needs its name or other information to label a report or a message.

When to use it
after Watch Lists, to write a clear line about the new list in your team tracker.
Watch out
you need the list to already exist; to browse every list, use List All Lists instead.
EmailOctopus8

Get Campaign Report: Summary

Action

In Make“Gets a summary of the campaign.”

Pulls the summary report of a sent campaign, the figures your team usually copies by hand into a deck or a spreadsheet after each send.

When to use it
feeding a reporting sheet or posting the results of a campaign in a team chat channel.
Watch out
run it once the campaign has actually gone out, or the summary will have little to show.
EmailOctopus9

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Covers what the other EmailOctopus modules do not: you call any endpoint of the EmailOctopus API yourself, and Make signs the request with the connection you already set up.

When to use it
you need an EmailOctopus feature that has no dedicated module in the list.
Watch out
you write the request by hand, so keep the EmailOctopus API documentation open next to the module.
EmailOctopus10

Update a Contact in a List

Action

In Make“Updates a contact of a list.”

Changes the record of someone already in a list, so your newsletter keeps the same data as your CRM or your shop when a detail changes over there.

When to use it
a customer edits their profile in another tool and EmailOctopus should follow.
Watch out
the contact must exist in that list; pair it with Get a Contact from a List when you are not sure.
EmailOctopus11

Update a List

Action

In Make“Updates a list.”

Edits an existing EmailOctopus list without touching its contacts, which saves a trip to the dashboard when the source of truth lives in another tool.

When to use it
a project gets renamed in your project tool and its mailing list should carry the new name.
Watch out
map the list carefully, because the change lands on whichever list you point it to.
EmailOctopus12

Get Campaigns

Search

In Make“Gets details of all campaigns.”

Returns all your campaigns, each one as a separate bundle, so the next modules can process them one by one in a single run of the scenario.

When to use it
building a full history of campaigns in a sheet the first time you set up reporting.
Watch out
each bundle it returns costs an operation in the modules that follow it.
EmailOctopus13

Get Contacts from a List

Search

In Make“Gets details of all contacts of a list.”

Brings back every contact of one list as separate bundles, which lets you copy a whole audience to another tool or check each subscriber against another source.

When to use it
migrating a list into a CRM or auditing who is still subscribed.
Watch out
a search can return zero, one or many contacts, and a big list means many operations downstream.
EmailOctopus14

List All Lists

Search

In Make“Get details of all the lists.”

Returns every list in your EmailOctopus account, one bundle per list, so you can loop over your audiences without naming them one at a time.

When to use it
producing an overview of all lists for a team dashboard, often followed by Get a List.
Watch out
add a filter after it when only some lists matter, or every later module will run for each of them.
Need help

Need help automating EmailOctopus with Make?

A person reads every message.

FAQ

EmailOctopus and Make: common questions

01Is the EmailOctopus Make integration free?
Yes, on the Make side. EmailOctopus is a standard app, so it works on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. Your EmailOctopus subscription is separate: check the EmailOctopus pricing page for what your account includes.
02What do you need to connect EmailOctopus to Make?
You need an active EmailOctopus account and an API key. In EmailOctopus, open the API key screen from the dashboard, click Add key, name the key, click Create and copy the key from the window that appears. In Make, add any EmailOctopus module, click Create a connection, optionally fill in a connection name, and paste the key. Every EmailOctopus module in your scenarios then reuses that connection, so you only do this once per account.
03Do EmailOctopus triggers in Make react in real time?
No. All 3 EmailOctopus triggers, Watch Campaigns, Watch Contacts and Watch Lists, are scheduled triggers. Make checks EmailOctopus on the schedule you set on the first module, every 15 minutes by default for a new scenario. On the Free plan the shortest interval is 15 minutes; paid plans go down to 1 minute. New campaigns, contacts or lists are picked up on the next check, not the second they appear.
04What if the EmailOctopus Make module you need is missing?
Use Make an API Call. It is one of the 17 EmailOctopus modules, and it lets you call any endpoint of the EmailOctopus API from your scenario with the connection you already created. You write the request yourself, so keep the EmailOctopus API documentation at hand. If the gap sits in another tool of your workflow, look for that tool's own Make app and add its modules to the same scenario.
05Should you use Make or n8n for EmailOctopus?
It depends on what your workflow needs. In Make, EmailOctopus comes with 17 modules, including 3 scheduled triggers and Make an API Call for anything else, and it runs on the Free plan. Many apps also have an n8n node, so check whether one exists for EmailOctopus and whether it covers the same actions. Then compare both tools on the modules you actually need rather than on the brand or on habit.
Same platform

Other docs you might need on this stack.

Browse all integrations