Resources · n8n integration

Mandrill n8n integrationAutomate Mandrill with n8n.

Mandrill sends the email your workflow just decided to send. The Mandrill n8n integration exposes a single Message resource with 2 operations, one for a saved template and one for raw HTML. No trigger node comes with it, so a Schedule Trigger or a Webhook opens the run.

Try the Mandrill integration on n8nSee the 2 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What the Mandrill n8n integration actually covers

The Mandrill n8n integration wires the transactional email service behind Mailchimp into a workflow, through a node that n8n ships by default. It covers one job: sending. The node exposes 1 resource, Message, and 2 operations, and it has no trigger of its own, so it always sits after another node that decided an email should go out.

The first scenario is the one the node was built for. A row lands in Google Sheets after a purchase, the workflow reads it, and message.sendTemplate fires the confirmation using a template stored in Mandrill. The workflow carries the data, Mandrill carries the wording, and the two stay separate.

The second one starts from content the workflow builds itself. A report, a weekly digest, a reminder assembled from several sources: the HTML exists only for that execution, so message.sendHtml posts it directly instead of asking anyone to maintain a template. Merge Vars still work, and so do attachments, headers and metadata.

The third is the quiet one. A lead moves forward in Mautic, the workflow sends the follow up through Mandrill and drops a line in Slack for the sales team. Mandrill handles the customer facing email here, while Gmail stays for the human replies that need a real mailbox behind them.

Where it stops is easy to state. Two operations, both on Message. The rest of the Mailchimp Transactional API is not in the node. The HTTP Request node calls any endpoint of that API and reuses the same credential through its predefined authentication, so the missing calls stay in the same workflow instead of moving somewhere else. If a project needs a second sending path, SendGrid has its own node with its own resources.

One more thing worth knowing before building: several parameters that feel mandatory, Subject and HTML among them, live inside the Options collection and stay empty until set. The n8n review goes into how that pattern repeats across nodes.

Connect

How do you connect Mandrill to n8n?

  1. 01

    Open the transactional account

    Mandrill is the transactional side of Mailchimp, so the account comes from there. Create a Mailchimp Transactional email account, then log in to Mandrill with those Mailchimp credentials. If a Mailchimp account already exists on a Standard plan or higher, turn on Transactional Emails inside it rather than opening a second account.

  2. 02

    Generate the API key

    In Mandrill, open Settings and generate an API key. That key is the only thing the node authenticates with: there is no OAuth flow here and no authentication selector on the node itself. Copy the key as soon as it appears, and keep the Settings page open until the credential is saved on the n8n side.

  3. 03

    Create the credential in n8n

    In n8n, open the Credentials menu, create a Mandrill credential and paste the API Key. A credential is set up once and reused by every workflow, and the node then offers it in its dropdown, so a second sending workflow needs no new setup. Name it after the sending account it points to.

Actions

What the Mandrill node can do

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

Resources × operations matrix
ResourceSend HTMLSend Template
Message✓✓

Message

2 operations
01

Send a message based on a template

message.sendTemplate

What you see in n8n

Notes & use cases

Sends an email from a template already saved in Mandrill and returns the status reported for each recipient.

Key parameters

  • Template Name or ID: the template to send, picked from the list n8n loads, or set with an expression such as {{ $json.template }}.
  • From Email: the sender address, with an optional name in the Admin <example@yourdomain.com> form.
  • To Email: the recipient, or several recipients separated by a comma.
  • Merge Vars: the values that fill the template placeholders, global for the send or set recipient by recipient.
Use cases
an order confirmation whose wording stays in Mandrill, editable without reopening the workflow.
02

Send a message based on HTML

message.sendHtml

What you see in n8n

Notes & use cases

Here the body travels with the execution: n8n posts the HTML assembled in the earlier nodes, so nothing has to exist in Mandrill beforehand.

Key parameters

  • From Email: the address the message comes from, required even when the HTML carries its own signature.
  • To Email: the destination, comma separated for a short internal list.
  • HTML: the body itself, found in the Options collection and its 24 fields, often {{ $json.html }}.
  • Subject: also under Options, and empty unless set, so a recurring send has to build it.
Use cases
a morning digest rendered from spreadsheet rows, with different content every day.
Need help

Need help automating Mandrill with n8n?

A person reads every message.

FAQ

Mandrill and n8n, the questions that come next

01Is the Mandrill n8n integration free?
Yes on the n8n side. The Mandrill node ships with n8n, on n8n Cloud and on a self hosted instance under the Community Edition and its Sustainable Use license, so there is nothing to install and no extra n8n cost for the 2 operations. What the sending itself costs depends on your own Mailchimp Transactional account, and this page does not cover that side. The credential is created once in the Credentials menu and reused by every workflow that sends through Mandrill, which keeps the setup work to a single pass even across several projects.
02What credentials does the Mandrill node need?
An API key, and nothing else. There is no authentication selector on the node: you create a Mandrill credential, paste an API Key generated from the Mandrill Settings page, and pick that credential in the node dropdown. Before that step you need a Mailchimp Transactional email account, or Transactional Emails switched on inside an existing Mailchimp account on a Standard plan or higher, since the Mandrill login goes through Mailchimp. Once saved, the same credential serves both operations, and any other workflow that needs to send. No scope list to tick, no consent screen.
03What are the limits of the Mandrill node in n8n?
It sends, and that is the whole scope. The node exposes 1 resource, Message, with 2 operations: one based on a saved template, one based on HTML. Every other Mailchimp Transactional endpoint sits outside it. For those, the HTTP Request node calls any endpoint of the API and reuses the same credential through its predefined authentication, so the workflow stays in one piece. Attachments, metadata, headers and tracking options do exist, but as parameters of a send rather than as operations of their own.
04Can a workflow start from Mandrill in n8n?
No. Mandrill has no trigger node in n8n, so nothing happening on the Mandrill side can open a run. A workflow that sends through Mandrill starts with something else: a Schedule Trigger firing at a fixed interval, an n8n Webhook, which is a URL a third party service calls to hand data over, or the trigger of another tool further up the chain. In practice the Mandrill node sits at the end, after the node that worked out who receives the email and what it says. That order also makes testing easier.
05n8n or Make for sending with Mandrill?
It depends on where the data has to live. n8n runs on your own server through Docker or npm, or on n8n Cloud, the hosted offer from n8n, and a workflow behaves the same either way. Make is hosted only, with no self hosting option, and bills per operation, which changes the arithmetic of a loop that sends many messages. Make reads well for a linear scenario, n8n for branching, expressions and code steps. For Mandrill both end up on the same API, so the decision is about hosting, data control and cost model rather than features.
Same platform

Other docs you might need on this stack.

Browse all integrations