Short answer: You can send transactional email in Brevo by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Brevo Send Transactional Email action to a workflow, map its 7 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 |
|---|---|---|---|
To Email to_email | string | Required | Recipient email address |
To Name to_name | string | Optional | Recipient display name |
Sender Email sender_email | string | Required | Must be a verified sender in your Brevo account |
Sender Name sender_name | string | Optional | Sender Name. e.g. "Your Company" |
Subject subject | string | Required | Subject. Example: Your order has been confirmed |
HTML Content htmlContent | string | Required | HTML body of the email |
Reply-To Email reply_to_email | string | Optional | Email address for replies |
{"to_email": "recipient@example.com","to_name": "John Doe","sender_email": "noreply@yourcompany.com","sender_name": "Your Company","subject": "e.g. Your order has been confirmed"}
{"messageId": "<202401010000.abc123@smtp-relay.brevo.com>"}
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.