Resources · Make integration

MailerSend Make integrationAutomate MailerSend with Make.

Get a transactional email out when something happens in another tool. The MailerSend Make integration gives you 2 action modules and no trigger, so another app starts the flow. This guide links your account and walks you through a first working scenario.

Try the MailerSend integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the MailerSend Make integration do for you?

It lets Make send emails through your MailerSend account whenever another tool reports an event. In Make, a scenario is the automation you build: a chain of modules, where each module is one brick, such as a trigger or an action. MailerSend brings two action bricks, and the starting signal comes from elsewhere.

Confirm a booking without lifting a finger. An appointment tool fires first, then Send an Email mails the client a confirmation built from the booking details. The Acuity Scheduling Make integration is one way to start that chain.

Tell a customer their record changed. When a row is updated in a base such as the one described in the Airtable Make integration, Make passes the row as a bundle, one item moving from module to module, and MailerSend sends the notice.

Reach parts of MailerSend the list does not show. Make an API Call talks to any endpoint of the MailerSend API with the same connection, so you are not stuck with sending only.

What Make does not do here: it cannot start a scenario from a MailerSend event, because the app has no trigger module. Plan the start on another app or on a schedule. The same app often has an n8n node too; the n8n vs Make comparison helps you weigh both tools.

Connect

How do you connect MailerSend to Make?

  1. 01

    Get your API key

    Log in to your active MailerSend account and generate an API key there. This key is what lets the scenario send in your name, so keep it somewhere private.

  2. 02

    Open the connection window

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

  3. 03

    Paste the key and save

    Paste the API key you copied from MailerSend into the connection window and save. The module now shows the connection as selected, and you can move on to filling its fields.

First scenario

Your first scenario with MailerSend

GoalWhen a new entry arrives in another app, Make sends a MailerSend email built from that entry.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app where the event starts, for example your form tool or spreadsheet, and choose its module.

  2. 02

    Add Send an Email

    Click the + on the right of that first module, search for MailerSend and pick Send an Email. Select the connection you created, or click Create a connection now.

  3. 03

    Map the entry into the email

    Fill the module fields by mapping data from the first module: the address and the details the reader should see come straight from the incoming bundle, with no copying by hand.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open the bubble on each module to read the bundles it received and check that the email reached the right inbox.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. Each module run on one bundle counts as one operation on your plan.

Modules

What the MailerSend modules do

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

MailerSend1

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

This module opens the whole MailerSend API to your scenario, reusing the connection you already set up, so you can reach an endpoint that has no ready-made module.

When to use it
pick it when Send an Email does not cover the task and the MailerSend API documentation shows an endpoint that does.
Watch out
you build the request yourself, so read the API reference first and test every call with Run once.
MailerSend2

Send an Email

Action

In Make“Sends an email.”

Your scenario gets a real email out through MailerSend, filled with data mapped from the modules that ran before it, so each recipient sees their own details.

When to use it
right after the event that deserves a message, such as a signed form or a paid order in another app.
Watch out
if your template still uses the old variable syntax, switch it to {{variable_name}} in MailerSend first.
Need help

Need help automating MailerSend with Make?

A person reads every message.

FAQ

MailerSend and Make: common questions

01Is the MailerSend Make integration free?
Yes, on the Make side. MailerSend is a standard app, so it is available on the Free plan, which allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 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. Usage is counted in credits, one operation per module run on one bundle. You still need an active MailerSend account, whose own subscription is separate from Make.
02What do you need to connect MailerSend to Make?
An active MailerSend account and an API key generated inside it. In Make, add a MailerSend module, click Create a connection, paste the key and save. That connection is stored once and reused by both MailerSend modules, so you never enter the key again for this account. Before testing, check your templates: since November 1, MailerSend expects variables written in the {{variable_name}} format, and older templates must be edited and saved in MailerSend under Email, then Templates, then Manage.
03Can a MailerSend scenario start in real time?
Not from MailerSend itself, because the app offers no trigger module in Make. The scenario has to begin somewhere else. You can open it with the trigger of another app, such as a form, a CRM or a spreadsheet, and let Send an Email follow. You can also start it on a schedule set with the clock of the first module, every 15 minutes by default, or as often as every minute on a paid plan. Whether that start reacts instantly depends on the other app's trigger type.
04What if the MailerSend module you need is missing in Make?
Use Make an API Call. It sends an authorized request to any endpoint of the MailerSend API with the connection you already created, which covers everything beyond Send an Email. You write the request yourself from the MailerSend API documentation, then check the result with Run once. If an existing scenario suddenly fails, look at the template variables first: the move to the {{variable_name}} format affects all MailerSend modules, and the fix happens in MailerSend, not in Make.
05Should you use Make or n8n for MailerSend?
It depends on the tool your team already runs. In Make, MailerSend comes with 2 modules, Send an Email and Make an API Call, and the second one reaches any endpoint of the API, so coverage is broad even with a short list. The same app often has an n8n node as well. Compare what each tool offers for your exact use case, open both editors, and pick the one where your other apps and your team's habits already live. The site's n8n vs Make comparison lays out the general differences.
Same platform

Other docs you might need on this stack.

Browse all integrations