Send Raw MIME

mandrill.send_raw
ActionEmailconnection required

Calls the Mandrill API with the connection's credentials.

Send a complete MIME document exactly as written, for mail another system has already assembled.

Connection

Required
Yes — the node will not save without one
Auth type
API key
Providers
Mandrill
Secret shape
the API key, or {"api_key": "…"}
Config it needs
base_url, from_email, from_name, subaccount, ip_pool
Resolved by
config.connection_id, else node.connection_id

Configuration

8 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
raw_message
The full MIME document, headers and body included.
stringYes———
to
Bare addresses to deliver to, as one address, a comma-separated list or an array. Leave empty to use the To, Cc and Bcc headers inside the document.
anyNo———
from_email
Sender address, overriding the document's own From header; falls back to the connection's default.
stringNo—email format—
from_name
Display name for the sender, overriding the document's.
stringNo———
return_path_domain
A custom domain to use for the message's return path.
stringNo———
async_send
Send in Mandrill's bulk background mode, which returns 'queued' for every recipient immediately. Messages to more than 10 recipients are always sent this way.
booleanNo———
ip_pool
Name of the dedicated IP pool to send from; falls back to the connection's pool, then to the account default.
stringNo———
send_at
Schedule the message for this UTC time, in YYYY-MM-DD HH:MM:SS format. A past time sends immediately; a future one is limited to a year out and requires a paid account.
stringNo——2026-10-01 09:00:00

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "send_at": "2026-10-01 09:00:00"
}

Output

One shape.

result

FieldTypeExample
results
One entry per recipient, as Mandrill returned it: email, status, _id and reject_reason.
array—
count
How many recipient results came back.
number—
accepted
True when Mandrill took every recipient (sent, queued or scheduled) and rejected none.
boolean—
message_ids
The _id Mandrill assigned to each recipient's message, rejected recipients included.
array—
status_counts
How many recipients landed in each Mandrill status (sent, queued, scheduled, rejected, invalid).
object—
rejected
The recipients Mandrill refused, each with its status and reject_reason.
array—
{
  "accepted": false,
  "count": 0,
  "message_ids": [],
  "rejected": [],
  "results": [],
  "status_counts": {}
}

Notes

  • Mandrill takes only bare addresses in 'to'; display names belong in the MIME.

See Send Raw MIME run in a workflow.

In a technical demo we add the Mandrill connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.