Short answer: You can send transactional email in Acumbamail by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Acumbamail Send Transactional Email action to a workflow, map its 5 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 | The email address. Used as the recipient or identifier depending on context. |
From Name from_name | string | Optional | Acme Support |
To Email to_email | string | Required | The email address. Used as the recipient or identifier depending on context. |
Subject subject | string | Required | Message subject line. |
HTML Body body | string | Required | Message body content. Plain text unless the API specifies HTML/markdown. |
{"from_email": "no-reply@acme.com","from_name": "Acme Support","to_email": "user@example.com","subject": "e.g. Quick update","body": "e.g. Hi there, thanks for reaching out."}
{"id": "msg_abc123","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.