Resources · Make integration

Mailrelay Make integrationAutomate Mailrelay with Make.

Can Make keep your Mailrelay lists up to date on its own? The Mailrelay Make integration gives you 11 modules to manage groups and subscribers from your other tools. This guide walks marketers through the connection, a first scenario and every module.

Try the Mailrelay integration on MakeSee the 11 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Mailrelay Make integration do for you?

The Mailrelay Make integration links your Mailrelay account to Make so that other apps can add, update, find or remove your subscribers and groups without anyone touching Mailrelay. You build a scenario, the automation itself, out of modules, each module being one brick that performs a single action or search.

Signups that reach your list by themselves. A form, a shop or a CRM passes each new contact to Create / Update a Subscriber, which adds the person or refreshes the record already there. Nobody exports a file to import it later.

A clean exit when someone asks to leave. When a customer closes their account in another tool, Search Subscribers finds them and Delete a Subscriber takes them out, so your lists match what the rest of the business knows.

Audiences ready before the campaign. Create a Group sets up a dedicated audience when a new offer or event is announced, and Update a Group or Delete a Group keeps that list of audiences tidy afterwards.

One thing to know up front: the Mailrelay app in Make has no trigger module, so Mailrelay itself never starts a scenario. The flow begins in another app or on a schedule, then Mailrelay receives the work. If you are still weighing tools, the Make review and the n8n vs Make comparison set out the criteria, and Make pricing explains how operations are counted.

Connect

How do you connect Mailrelay to Make?

  1. 01

    Copy your API key in Mailrelay

    Log in to Mailrelay, open Settings then API Keys, and copy the token shown there. Keep that tab open: you will paste the token into Make in the next step.

  2. 02

    Open the connection dialog in Make

    Add any Mailrelay module to a scenario and click Create a connection. Give it a clear name in Connection name, then paste the token into API Key. A connection is your Mailrelay account linked once, reused by every Mailrelay module.

  3. 03

    Enter your domain and confirm

    In Domain, type the name your Mailrelay account uses in its web address, then click Continue. Make can now read and change your groups and subscribers from any scenario.

First scenario

Build your first scenario: new signups straight into Mailrelay

GoalWhen another app records a new contact, Make creates or updates that person as a subscriber in Mailrelay.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + in the middle of the editor to place the first module.

  2. 02

    Start from the app where contacts appear

    Pick the trigger of the tool that collects your contacts, a form or a shop for example. Mailrelay has no trigger, so this other app is what sets the scenario in motion.

  3. 03

    Add Create / Update a Subscriber

    Click the + on the right of the first module, search for Mailrelay and choose Create / Update a Subscriber. Select your connection, or create it with the steps above.

  4. 04

    Map the contact data

    Fill the module by mapping the values that come out of the first module. Each bundle, one contact here, then becomes one subscriber in Mailrelay.

  5. 05

    Test with Run once

    Click Run once and create a test contact in the source app. Open the bubble above each module to read the bundles it received, then check the subscriber in Mailrelay.

  6. 06

    Schedule and switch it on

    Set the schedule on the first module, every 15 minutes by default and never below that on the Free plan, then switch the scenario on. Each module run counts as one operation.

Modules

What each Mailrelay module does in Make

Mailrelay gives you 11 modules in 4 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Groups

5 modules
Mailrelay1

Search Groups

Search

In Make“Searches for groups or lists them all.”

Search Groups brings back the groups of your Mailrelay account, either all of them or only those matching your search, and passes each one to the next module as its own bundle.

When to use it
a later step needs a group ID and you only know which group you are after, or you want to review every group in one pass.
Watch out
the result can hold zero, one or several groups, so read what Run once returned before chaining an action that changes data.
Mailrelay2

Get a Group

Action

In Make“Retrieves a single group specified by ID.”

Get a Group reads the details of one group you already know by its ID, which saves a search when another tool of yours stores that ID and you need the rest before acting.

When to use it
choose it over Search Groups when the ID is already in hand, because the result is a single bundle instead of a list.
Watch out
the module works from the ID alone, so map it from an earlier module rather than typing a fixed value.
Mailrelay3

Create a Group

Action

In Make“Creates a new group.”

Create a Group adds a fresh group to Mailrelay, so a new audience exists before the first subscriber lands in it and nobody has to set it up by hand.

When to use it
you announce a webinar or a product launch and want its own mailing audience.
Watch out
Run once performs the action for real, so every test leaves a new group in your account; tidy up in Mailrelay afterwards.
Mailrelay4

Update a Group

Action

In Make“Updates a group specified by ID.”

Update a Group changes an existing group, picked by its ID, so the audience in Mailrelay keeps pace with decisions taken elsewhere in your tools.

When to use it
a segment in your CRM changes purpose and the matching Mailrelay group should follow without anyone editing it twice.
Watch out
it targets one ID per run; to update several groups, place Search Groups in front so each group found arrives as its own bundle.
Mailrelay5

Delete a Group

Action

In Make“Removes a group specified by ID.”

Delete a Group removes a group from your Mailrelay account by its ID, which keeps your list of audiences short once a campaign or an event is over.

When to use it
at the end of a flow that closes an offer, once the group attached to it no longer serves any sending.
Watch out
nothing in Make brings a deleted group back, so test with a throwaway group before pointing the module at a real one.

Subscribers

4 modules
Mailrelay6

Search Subscribers

Search

In Make“Searches for subscribers or lists them all.”

Search Subscribers finds contacts in Mailrelay, or lists every one of them, and returns each match as a separate bundle the next step can work on.

When to use it
you need to know whether someone is already on your lists, or you need their ID before deleting them or resending a confirmation.
Watch out
a broad search can return many subscribers, and each of them costs one operation in every module that follows.
Mailrelay7

Get a Subscriber

Action

In Make“Retrieves a subscriber specified by ID.”

Get a Subscriber fetches the full record of one contact when you already hold their Mailrelay ID, giving the modules after it everything Mailrelay knows about that person.

When to use it
prefer it to Search Subscribers when the ID is saved in another tool, a CRM record or a spreadsheet row for instance.
Watch out
it only accepts the ID; if you start from anything else, Search Subscribers is the module that will find the person.
Mailrelay8

Create / Update a Subscriber

Action

In Make“Creates a new subscriber or updates an existing one.”

Create / Update a Subscriber adds a new contact to Mailrelay or refreshes the one already there, in a single module, so you never check first whether the person exists.

When to use it
this is the module for signup forms, shop checkouts and CRM changes, the everyday work of keeping lists current.
Watch out
since the same module also updates, a wrong mapping can alter an existing contact; run your first tests on a test address.
Mailrelay9

Delete a Subscriber

Action

In Make“Removes a subscriber specified by ID.”

Delete a Subscriber takes one contact out of your Mailrelay account by ID, which is how a removal request made in another tool actually reaches your mailing lists.

When to use it
a customer asks to be erased or closes their account on your side, after Search Subscribers has returned their ID.
Watch out
the removal cannot be undone from Make, so keep this module at the very end of the flow and try it on a dummy subscriber.

Confirmation Emails

1 module
Mailrelay10

Resend a Confirmation Email

Action

In Make“Resends a confirmation email to a subscriber specified by ID.”

Resend a Confirmation Email sends the confirmation message again to one subscriber, picked by ID, giving a signup that stalled a second chance to be confirmed.

When to use it
a follow up flow for people who registered through your form but never confirmed their address after the first message.
Watch out
every run mails a real person, so keep Run once tests on your own address and avoid placing it after a search that returns everyone.

Other

1 module
Mailrelay11

Make an API Call

Action

In Make“Performs an arbitary authorized API call.”

Make an API Call opens any part of the Mailrelay API that the ten other modules leave out, and it reuses the connection you already set up, so there is no second login.

When to use it
the task you have in mind is not covered by the listed modules but exists in the Mailrelay API.
Watch out
you write the request yourself, so keep the Mailrelay API reference open while you fill the module.
Need help

Need help automating Mailrelay with Make?

A person reads every message.

FAQ

Mailrelay and Make: common questions

01Is the Mailrelay Make integration free?
Yes. Mailrelay is a standard app in Make, available from the Free plan onward. The Free plan allows 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) lower the minimum interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one per module run on each bundle.
02What do you need to connect Mailrelay to Make?
A Mailrelay account and its API key are enough, since the documentation lists no other prerequisite. In Mailrelay, open Settings, then API Keys, and copy the token. In Make, click Create a connection on any Mailrelay module, name the connection, paste the token into API Key and enter your account domain, the part before .ipzmarketing.com in your Mailrelay address. Click Continue and the connection is shared by every Mailrelay module in your scenarios.
03Does Mailrelay trigger Make scenarios in real time?
No, because the Mailrelay app in Make has no trigger module at all. A scenario that works on Mailrelay starts elsewhere: either on the trigger of another app, such as a form or a shop, which may be scheduled or instant depending on that app, or on the schedule of the first module, every 15 minutes by default. An instant trigger is one the other app calls through a webhook as soon as something happens; a scheduled one is polled by Make.
04What if a Mailrelay module is missing in Make?
Use Make an API Call. The 11 modules cover groups, subscribers and confirmation emails, and when you need something else from the Mailrelay API, this module calls any endpoint with the same connection, so you do not reconnect your account. The documentation lists no numbered limit for the Mailrelay app. If a scenario fails for another reason, start by opening the bundles shown after Run once to see which module stopped and why.
05Make or n8n for Mailrelay?
It depends on the tool your team already runs its automations in. On Make, Mailrelay comes with 11 ready modules plus Make an API Call, a guided connection by API key and the same editor as every other app of your stack. The same app often has a node in n8n as well, so check which modules each side offers for the job you have in mind before you choose. Neither choice is ranked here: compare features and the way each tool counts usage.
Same platform

Other docs you might need on this stack.

Browse all integrations