Short answer: You can mandrill send template email in Mandrill by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Mandrill Mandrill Send Template 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 |
|---|---|---|---|
Template Name template_name | string | Required | Template Name. Example: welcome-email |
To Email to_email | string | Required | To Email. e.g. "user@example.com" |
To Name to_name | string | Optional | To Name. e.g. "John Doe" |
From Email from_email | string | Required | From Email. e.g. "noreply@company.com" |
Subject subject | string | Required | Message subject line. |
Template Variables (JSON) merge_vars | string | Optional | Array of name/content pairs |
{"template_name": "e.g. welcome-email","to_email": "user@example.com","to_name": "John Doe","from_email": "noreply@company.com","subject": "e.g. Quick update"}
[{"_id": "abc123","email": "user@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.