Short answer: Drop the "Mandrill → Mandrill Send Email" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
From Email from_email | string | Required | From Email. e.g. "noreply@yourdomain.com" |
From Name from_name | string | Optional | From Name. e.g. "Your Company" |
To Email to_email | string | Required | To Email. e.g. "recipient@example.com" |
To Name to_name | string | Optional | To Name. e.g. "John Doe" |
Subject subject | string | Required | Subject. Example: Your order is confirmed |
HTML Body html | string | Required | HTML Body |
{"from_email": "noreply@yourdomain.com","from_name": "Your Company","to_email": "recipient@example.com","to_name": "John Doe","subject": "e.g. Your order is confirmed"}
[{"_id": "abc123","email": "recipient@example.com","status": "sent"}]
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.