Short answer: You can mandrill send email in Mandrill by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Mandrill Mandrill Send Email action to a workflow, map its 6 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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.