Resources · n8n integration

Mailjet n8n integrationAutomate Mailjet with n8n.

Can one workflow send the message and handle what comes back? That is the job of the Mailjet n8n integration. The node covers 3 operations across 2 resources, email, templated email and SMS. The trigger listens to 6 events, from sent to unsub. Useful when transactional mail runs without a developer on call.

Try the Mailjet integration on n8n See the 3 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Mailjet n8n integration actually do?

Two nodes, two directions. The Mailjet node pushes messages out: 3 operations spread over the Email and SMS resources. The Mailjet Trigger listens the other way, catching the 6 events Mailjet reports on a message through a webhook, a URL that n8n registers so Mailjet can call it the moment something happens. The same credential serves both, and it is created once in the n8n Credentials menu.

Take a shipping notice. An order moves to shipped in your database, a workflow picks it up, and email.sendTemplate fires a design the marketing team already built in Mailjet. n8n supplies the tracking number as a variable, nothing else. The wording stays where the people who own the wording can edit it, which keeps developers out of copy review.

Second pattern: a short SMS where an email would be too slow. A failed payment, a delivery window, a code that expires. sms.send takes a sender name, a number in international format and the text, and that is the whole node. Teams often chain it after a Google Sheets lookup that holds the phone numbers.

Third pattern runs backwards. The trigger catches a bounce or a blocked event, n8n writes the address to a sheet, flags the contact in Mautic and drops a line in Slack when the same domain fails twice in a day. List hygiene stops being a monthly chore nobody enjoys.

Where the node stops, HTTP Request takes over. The Mailjet node sends, and only sends. Contact lists, segments, campaign drafts and statistics are not exposed as operations, so anything in that territory goes through the HTTP Request node, which calls any Mailjet endpoint while reusing the credential you already saved. Same authentication, no second setup.

Two limits worth knowing before you build. The trigger has no wildcard value, so one trigger node listens to one event and a workflow that cares about four events needs four of them. And the SMS side uses a different credential type from the email side, which surprises people who assumed one key would cover the account. If you are still comparing tools, the SendGrid and Gmail nodes sit in the same family and solve a different slice of the same problem.

Connect

How do you connect Mailjet to n8n?

01
Pick the right credential type
Mailjet exposes two authentication methods and n8n mirrors both. Email API key covers everything on the Email API, so the send and send template operations plus the trigger. SMS token covers the SMS API and nothing else. Decide by operation, not by account: a workflow that emails and texts needs both credentials saved, and each node picks its own from the dropdown.
02
Copy the API Key and Secret Key
For the email credential, n8n asks for an API Key and a Secret Key. Both are visible in the API Key Management page of your Mailjet account. The primary pair works, and so does a subaccount pair if you would rather keep the automation traffic separate from the rest. A credential is created once in the Credentials menu and reused by every workflow after that.
03
Generate the SMS token if you need it
The SMS credential wants a single access Token, generated from the SMS Dashboard in Mailjet. It carries no secret key and no sandbox switch. Save it under its own name, something that says sms out loud, because the node dropdown lists credentials by name and picking the email one on an SMS node produces an authentication error rather than a helpful hint.

Triggers

What starts a workflow from Mailjet ?

Mailjet Trigger is the node that starts a workflow when something happens in Mailjet. It listens to 6 events, listed below by family. Pick one or several, activate the workflow: n8n registers the webhook on your Mailjet account.

What you see in n8n

Every event, by family

One row per object, one chip per action. The event to tick in the node is object.action; hover a chip to read exactly when it fires.

blocked.*1

blocked.
- blocked

bounce.*1

bounce.
- bounce

open.*1

open.
- open

sent.*1

sent.
- sent

spam.*1

spam.
- spam

unsub.*1

unsub.
- unsub

Configuration notes

01Set up the Mailjet TriggerThe trigger node has a single setting, and that setting decides everything the workflow reacts to. Activate the workflow and n8n registers a webhook, a public URL that Mailjet calls as soon as something happens to a message, so events land within seconds instead of being fetched on a schedule.

The trigger node has a single setting, and that setting decides everything the workflow reacts to. Activate the workflow and n8n registers a webhook, a public URL that Mailjet calls as soon as something happens to a message, so events land within seconds instead of being fetched on a schedule.

Key parameters

Event: the one event this node listens to, chosen among the 6 values Mailjet reports: sent, open, bounce, blocked, spam and unsub.

When to use it

whenever the workflow should start from Mailjet rather than from your own application. There is no wildcard option, so plan one trigger node per event, either in separate workflows or side by side in the same canvas. The trigger node is version 1 and takes no other parameter, which also means there is nothing to tune if events arrive faster than expected.

02sentMailjet reports sent once a message has been accepted and handed to the receiving server. It confirms departure, not reading, and it is the cheapest proof you have that a workflow actually did what it claimed.

Mailjet reports sent once a message has been accepted and handed to the receiving server. It confirms departure, not reading, and it is the cheapest proof you have that a workflow actually did what it claimed.

Key parameters

Event: set to sent on a trigger dedicated to delivery confirmations.

When to use it

audit trails and silent failure detection. A workflow that emails every new invoice can log each sent event to a sheet, then compare that log against the invoices created the same day. A gap means a send died somewhere upstream, which is far easier to notice in a row count than in an inbox. It also makes a decent heartbeat when someone asks whether the automation is still running at all.

03bounce, blocked and spamThree events describe three ways a message fails. bounce means the receiving server rejected it, blocked means Mailjet refused to send it at all, and spam means a recipient pressed the complaint button. Each one damages sender reputation if you ignore it.

Three events describe three ways a message fails. bounce means the receiving server rejected it, blocked means Mailjet refused to send it at all, and spam means a recipient pressed the complaint button. Each one damages sender reputation if you ignore it.

Key parameters

Event: one trigger node per value, since the node accepts a single event and offers no wildcard.

When to use it

automatic list hygiene. Route all three into the same downstream branch, mark the contact in your database, and stop sending to that address. A complaint deserves a harder rule than a bounce, so a Switch node after the trigger usually pays for itself. Teams running weekly campaigns tend to wire the spam branch to an alert as well, because a sudden burst means the last send went to the wrong segment.

04open and unsubEngagement arrives through two events that pull in different directions. open fires when a recipient loads the message, unsub when they leave the list. Read together they tell you whether the content is landing or wearing people out, a different signal from the delivery failures the other events report.

Engagement arrives through two events that pull in different directions. open fires when a recipient loads the message, unsub when they leave the list. Read together they tell you whether the content is landing or wearing people out, a different signal from the delivery failures the other events report.

Key parameters

Event: open for interest signals, unsub for departures, each on its own trigger node, since a single trigger accepts one value with no option to catch both at once.

When to use it

lead scoring and retention watch. An open on a pricing email can raise a score in your CRM and notify the account owner the same minute, while unsub feeds a suppression list that every later workflow checks before sending a follow-up.

Actions

What can the Mailjet node do?

The Mailjet node exposes 3 operations across 2 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
Resource	Send	Send Template
Email	✓	✓
SMS	✓

Email

2 operations

Send an email

email.send

What you see in n8n

Notes & use cases

Builds a message field by field and hands it to the Email API, which returns the identifiers n8n passes down the workflow.

Key parameters

From Email: the sender address, shaped like admin@example.com, and it has to be a sender Mailjet already recognizes.
To Email: the recipient, or several separated by a comma, often {{ $json.email }} from the previous node.
HTML and Text: the rich body and the plain text fallback.
Additional Fields: holds Reply To, From Name, Cc Addresses and Track Opens.

Use cases

an internal alert assembled by a Code node, or a notice whose wording changes on every run and would never survive as a template.

Send an email template

email.sendTemplate

What you see in n8n

Notes & use cases

Reuses a design stored in Mailjet and injects data into it, so layout and copy stay with the people who own them.

Key parameters

Template Name or ID: picked from the dropdown, or supplied as an expression when the template depends on the item.
Variables: Name and Value pairs that fill the placeholders inside the design.
From Email and To Email: same addressing as a raw send.
Subject: overrides the subject line carried by the template.

Use cases

order confirmations, password resets, renewal reminders. Anything sent thousands of times where a typo would be expensive to fix one workflow at a time.

SMS

1 operation

Send an SMS

sms.send

What you see in n8n

Notes & use cases

Pushes a text message through the SMS API, using the SMS token credential rather than the email pair.

Key parameters

From: the sender name shown on the handset, 3 to 11 characters, alphanumeric only, so no spaces and no punctuation.
To: the recipient number in E.164 format, 3 to 15 characters, always starting with a plus sign and the country code.
Text: the message body, required, and the only content the recipient sees.

Use cases

a delivery window, an expiring code, an on-call escalation after an email has gone unread for an hour.

Need help

Need help automating Mailjet with n8n?

A person reads every message.

FAQ

Mailjet and n8n, common questions

01Is the Mailjet n8n integration free?

Yes, on the n8n side. Both the Mailjet node and the Mailjet Trigger ship with n8n, so there is nothing to install and nothing extra to pay, whether you run n8n Cloud or self-host the Community Edition under its Sustainable Use licence. A self-hosted instance on Docker or npm runs the exact same workflow as a Cloud one, and the JSON moves between them without edits. What Mailjet itself charges for sending email and SMS is a separate matter, decided by your Mailjet plan, and n8n has no influence over it.

02Which Mailjet credentials does n8n need?

Two methods exist and they are not interchangeable. The Email API key method asks for an API Key and a Secret Key, both found in the API Key Management page of your Mailjet account, and it covers the send operations plus the trigger. The SMS token method asks for a single access Token generated from the SMS Dashboard, and it covers the SMS operation only. Either the primary key pair or a subaccount pair works for the email credential. Each credential is saved once in the Credentials menu and then selected from a dropdown inside every node that needs it.

03What can the Mailjet node not do?

It sends, and that is the scope. The node exposes 3 operations over 2 resources, so email, templated email and SMS are covered, while contact lists, segments, campaign drafts, statistics and template management are not. For any of those, use the HTTP Request node: it calls any Mailjet endpoint directly and reuses the credential you already saved, so authentication is not rebuilt. The trigger has a matching limit on the other side, with no wildcard event value, which means one trigger node per event rather than one node listening to all 6 at once.

04Does the Mailjet Trigger react in real time?

Close to it. The trigger works by webhook, meaning n8n registers a URL with Mailjet when you activate the workflow, and Mailjet calls that URL as soon as an event occurs. Each event reaches the workflow within seconds, and nothing is polled on a schedule, so there is no interval to tune and no delay you chose by accident. One consequence is worth planning for: a deactivated workflow has no live webhook, so events that happen while it is off are not queued up for later. Keep production workflows active, and test on a separate one.

05n8n or Make for Mailjet?

It depends on three things. Hosting first: n8n can be self-hosted with Docker or npm, or run on n8n Cloud, while Make is hosted only, so if recipient addresses and message bodies cannot leave your infrastructure, that settles the question early. Cost model second: Make bills per operation, which adds up on a scenario that branches once per event type. Control third: n8n's HTTP Request node reaches any Mailjet endpoint the dedicated node skips, contact lists and segments included, while reusing the same credential. Make stays a solid visual editor for a scenario that stays linear, and the comparison runs both ways.

Pick the right credential type

Copy the API Key and Secret Key

Generate the SMS token if you need it

Every event, by family

Configuration notes

Need help automating Mailjet with n8n?