Resources · Zapier integration

MailerSend Zapier integrationAutomate MailerSend with Zapier.

MailerSend Zapier integration: 11 triggers, 3 actions and 0 searches. Every trigger is instant, the app is not premium, and the free plan covers a two-step Zap. Here is what each operation does, what it costs and the traps that stop a send.

See the 14 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the MailerSend Zapier integration actually does

MailerSend sends the transactional emails and the text messages your other tools hand over to it. Linked to Zapier, each delivery, open, click or bounce can start a Zap, the automation you build there, which runs one or more steps every time. Zapier can also send email and SMS through your MailerSend account.

A bounce list your team can act on. Email Is Hard Bounced fires for each address that rejected a message for good, and a spreadsheet step keeps the list up to date for whoever cleans your contacts.

A second channel when the first one fails. SMS Delivery Failed passes the failed message to Zapier, and Send an Email reaches the same person another way.

Messages started from anywhere. A form, a sheet or another tool can start the Zap, then Send a Template-Based Email or Send an SMS delivers a message you designed once in MailerSend.

What Zapier does not do here: there is no search step, so a Zap cannot look up a past message or a recipient in MailerSend, and the three actions only send; nothing creates templates, domains or numbers, and nothing reads your sending statistics. Events from before the Zap is published are not replayed. If you also use Make, see our MailerSend Make integration page and our Make vs Zapier comparison.

Vocabulary

Zapier vocabulary in one minute

Seven words come back on every line of this page. Here they are in plain terms.

Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for that event and nothing else.
Action
What the Zap does after it starts: the step that sends, writes or moves something on your behalf.
Task
The unit Zapier bills. One action that completes successfully is one task, and your plan is a count of those.
Instant trigger
A trigger the app reports itself, calling Zapier the moment the event happens. All 11 MailerSend triggers work this way.
Polling trigger
A trigger Zapier checks on a timer, asking the app for new items at a fixed interval. MailerSend has none.
Filter
A step that lets the Zap continue only when the incoming data meets a condition you set, and stops it otherwise.
Connection
Your MailerSend account linked to Zapier once, then reused by every step in every Zap that touches the app.
Cost

What it really costs

Zapier bills completed actions, not events. An open, a click or a bounce reaching Zapier costs nothing until an action runs.

  • Free plan100 tasks per month
  • Premium appNo, available on the free plan
  • Cost of a trigger0 tasks
  • Free plan Zap size2 steps: one trigger, one action

Each action that goes through counts as one task; a failed one is not counted. A three-action Zap uses three times what a one-action Zap uses. MailerSend is not a premium app, so the free plan (100 tasks a month) covers it, but only for two-step Zaps: one trigger, one action. Add a filter or a second action and you are building a multi-step Zap, which needs a paid plan. The interval grid below is the one Zapier applies to polling triggers; it does not apply to this app, whose 11 triggers are all instant.

Connect

Connect your MailerSend account

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. You need an existing MailerSend account, with access to the domains and numbers the Zap will use.

  2. 02

    Pick MailerSend

    Type MailerSend in the dialog, choose it in the results, then click Add connection. That button opens the sign-in tab used in the next step of this setup.

  3. 03

    Sign in and grant access

    Sign in to MailerSend in the tab that opens and allow Zapier to use the account. From then on, every Zap step that uses MailerSend reuses this connection.

First Zap

Your first Zap: keep a list of hard bounces

GoalWhen an email hard bounces on your domain, check the condition you care about, then add the address as a new row in your sheet.

  1. 01

    Pick the trigger

    Create a Zap, choose MailerSend as the app and Email Is Hard Bounced as the event, then select your connection and the domain to watch.

  2. 02

    Test it on real data

    Run the trigger test. Zapier brings back the three most recent items of the account, so you map the next steps on a real bounce rather than a blank example.

  3. 03

    Add the filter

    Click the plus icon, add Filter, then set the field to look at, the rule and the value in Configure & test. Text rules only work on text.

  4. 04

    Log the address

    Add your spreadsheet step with its new-row action and map the recipient address from the trigger into the right column of the sheet.

  5. 05

    Test and publish

    Test each step and read what came back, then click Publish. With a filter this is a multi-step Zap, so it needs a paid plan.

Triggers

MailerSend triggers

11 events start a Zap when something happens in MailerSend, and 11 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Email Is Clicked Through

Instant trigger

In Zapier“Triggers when the recipient clicks on a link.”

Fires each time a recipient clicks a link in one of your emails. It is the strongest sign of interest MailerSend can send to Zapier.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
flag the contact in your other tool, or alert a colleague, when someone clicks through a message.
Watch out
the Domain field is required, so one Zap follows the clicks of one sending domain only.
2

Email Is Delivered

Instant trigger

In Zapier“Triggers when an email is delivered.”

Confirms that an email reached the receiving server. Use it when you need proof of delivery rather than a guess.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
mark a message as delivered in the tool that asked for it, so nobody resends by mistake.
Watch out
Domain ID is required. On a busy domain every delivery starts a run, so keep the actions behind it cheap.
3

Email Is Hard Bounced

Instant trigger

In Zapier“Triggers when an email is hard bounced.”

Catches the emails that bounced for good, the kind of failure that will repeat if you write to that address again.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
build a list of dead addresses in a sheet, as in the first Zap above, and clean them out of your other tools.
Watch out
the Domain field is required; each sending domain needs its own Zap.
4

Email Is Opened

Instant trigger

In Zapier“Triggers when an email is opened.”

Reacts when a recipient opens one of your emails. Good for follow-ups that only make sense once the message has been seen.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
note the open on the matching record in another tool, so the next step of your process starts from a known point.
Watch out
the Domain field is required, and the same person can open a message more than once, each open starting the Zap.
5

Email Is Sent

Instant trigger

In Zapier“Triggers when an email is sent.”

Starts a Zap as soon as MailerSend sends an email from your domain, before anything is known about delivery.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
keep a sending log in a sheet for every message your tools push through MailerSend.
Watch out
Domain ID is required. A Zap that also uses Send an Email on that domain sets itself off with its own sends.
6

Email Is Soft Bounced

Instant trigger

In Zapier“Triggers when an email is soft bounced.”

Signals a temporary delivery failure: the address exists, but the message did not get through this time.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
reach the person through another channel, such as Send an SMS, when an important email did not land.
Watch out
Domain ID is required, and a soft bounce is not a dead address, so do not treat it like a hard bounce.
7

Email Is Reported as Spam

Instant trigger

In Zapier“Triggers when an email is reported as spam.”

Tells Zapier when a recipient reports one of your emails as spam. Rare, but each one deserves attention.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
stop writing to that person in your other tools and keep a written trace of the complaint.
Watch out
the Domain field is required, and with few complaints the trigger test may have nothing recent to bring back.
8

Recipient Has Unsubscribed

Instant trigger

In Zapier“Triggers when a recipient unsubscribes from your mailing activity.”

Fires when a recipient opts out of your mailing activity. The address reaches Zapier with the event.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
mark the contact as opted out in your other tools, so the choice they made holds everywhere.
Watch out
the Domain field is required, and the Zap only sees opt-outs made after it was switched on.
9

SMS Is Delivered

Instant trigger

In Zapier“Triggers when SMS is delivered.”

Confirms that a text message sent from one of your MailerSend numbers reached the phone it was meant for.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
close a reminder in another tool once the SMS has actually arrived, not just left.
Watch out
the SMS number ID field is required, so a Zap follows one sending number at a time.
10

SMS Delivery Failed

Instant trigger

In Zapier“Triggers when SMS failed to deliver.”

Reports a text message that could not be delivered. The Zap gets the failed message and can try something else.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
fall back to Send an Email so the person still gets the information, as in the Zap at the top of the page.
Watch out
SMS number ID is required, and a fallback email needs the address to be available somewhere in the Zap.
11

SMS Is Sent

Instant trigger

In Zapier“Triggers when SMS is sent.”

Fires the moment MailerSend sends a text message from the number you choose, whatever happens to it next.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
keep a log of every SMS that leaves your account, next to your email log.
Watch out
SMS number ID is required. A Zap that uses Send an SMS from that same number triggers itself.
Actions

MailerSend actions

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

1

Send an Email

Action

In Zapier“Send an email via your MailerSend account.”

Sends an email you compose in the Zap itself, with a sender, a recipient, a subject and a plain-text version. Several recipients go in one field, separated by commas.

When to use it
send a message whose content depends on what the trigger brought in.
Watch out
the sender address must belong to a domain verified in your MailerSend account.
2

Send a Template-Based Email

Action

In Zapier“Send an email based on a template via your MailerSend account.”

Delivers an email built from a template you already designed in MailerSend, so the layout stays the same every time.

When to use it
send a polished, branded message without rewriting it inside each Zap.
Watch out
the Template ID is required; copy it from the template page of your MailerSend account.
3

Send an SMS

Action

In Zapier“Send an SMS via your MailerSend account.”

Sends a text message from one of your MailerSend numbers to one or more phones, separated by commas.

When to use it
reach someone on their phone when an email is not enough or did not get through.
Watch out
phone numbers must be in E164 format and the message must stay at 2048 characters or less.
When it breaks

When it breaks

Most failures here come from sender settings and from Zaps that watch their own sends.

Here are the cases worth knowing before you publish. When a Zap stops for a reason you cannot place, see our Zapier troubleshooting guide.

  • The sender domain is not verified

    Send an Email needs a From address on a domain verified in your MailerSend account. An address on any other domain cannot be used as the sender.

  • Phone numbers in the wrong format

    Send an SMS expects each recipient number in the exact phone format the field asks for. A number stored another way in a sheet or a form will not match.

  • A text message that is too long

    The Text Message field of Send an SMS accepts 2048 characters or less. Long content mapped from another app has to be cut before this step.

  • The Zap watches its own sends

    A Zap started by Email Is Sent or SMS Is Sent that sends again from the same domain or number sets itself off, again and again, and burns tasks.

  • Nothing from before is picked up

    A Zap only reacts to events after it is switched on. Bounces, opens and opt-outs that already happened stay where they are; moving them is a separate job.

  • A large send floods the trigger

    A big batch of emails can produce a huge wave of delivery or open events, and Zapier's flood protection can hold that wave back.
Need help

Need help automating MailerSend with Zapier?

A person reads every message.

FAQ

MailerSend and Zapier: questions people ask

01Is the MailerSend Zapier integration free?
Yes, as long as the Zap has two steps. MailerSend is not a premium app, so it works on the free plan, which gives 100 tasks a month. The catch is the size of the Zap: the free plan allows one trigger and one action. A Zap that logs a hard bounce in a sheet fits; one that filters bounces first, or logs them and then emails a colleague, is a multi-step Zap and needs a paid plan.
02How many tasks does a MailerSend Zap use?
One task per action that succeeds, and nothing for the trigger. A bounce, an open or a click reaching Zapier costs zero; logging it in a sheet costs one task; sending a fallback email after that costs one more. A failed action, for instance an SMS refused because of the number format, is not counted. Triggers like Email Is Delivered or Email Is Opened can fire very often on a busy domain, so count the actions behind them and multiply by how often they fire.
03Does MailerSend trigger Zaps instantly?
Yes, all 11 triggers are instant. MailerSend tells Zapier the moment an email or an SMS event happens, so the Zap starts without waiting for a scheduled check, on every plan including the free one. The polling intervals of Zapier's plan grid do not apply to this app. In the editor, a Zap built on an instant trigger shows a lightning bolt, which is the quickest way to confirm it. Paying for a higher plan does not make these triggers any faster.
04What does it take to connect MailerSend to Zapier?
An existing MailerSend account and access to the domains and numbers the Zap will use. Open the Apps page in Zapier, click + Add connection, pick MailerSend, sign in in the tab that opens and grant access. Before building, check two things in MailerSend: a verified domain for the sender of Send an Email, and the template page where you copy the Template ID if you plan to use templates. Email triggers also ask you to choose a domain, and SMS triggers a sending number.
05Why does Send an SMS fail from a MailerSend Zap?
Usually because of the recipient number or the message length. The phone number has to follow the exact format the field describes, and several numbers go in one field separated by commas. A number stored another way in a sheet or a form will not match. The Text Message field is also capped at 2048 characters, so long content mapped from another app needs trimming first. The From SMS number field is required too, so pick your sending number before testing.
06What if the MailerSend operation you need is missing?
Then it is not offered on Zapier today. The integration has 11 triggers and three actions, all of them about sending: an email you write, an email from a template, or an SMS. There is no search step, so a Zap cannot look up a past message, and no action manages templates, domains or numbers. Anything outside sending and reacting to delivery events has to be done in MailerSend directly. List what the automation should do and match each point to one of these 14 operations.
07Zapier, Make or n8n for MailerSend?
Decide on criteria rather than on a name. On Zapier, check that the operations you need are among the 11 triggers and 3 actions listed here, that two steps are enough if you want to stay on the free plan, and that a task budget counted per successful action suits your sending volume. Instant triggers are a plus, since every delivery or bounce reaches Zapier straight away. If your process needs a lookup step, note that this integration has none, and compare how each tool handles that.
Same platform

Other docs you might need on this stack.

Browse all integrations