ActionBrevoUpdated September 2026

How do I send a transactional email via Brevo?

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.

Send Transactional Email in Brevo — start free All 9 Brevo actions

Send Transactional Email in Brevo — start free

Inputs

The fields this action accepts.

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

Sample request

{
  "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"
}

Returns

{
  "messageId": "<202401010000.abc123@smtp-relay.brevo.com>"
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Send Transactional Email.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Brevo

2 Google Sheets triggers

HubSpot → Brevo

18 HubSpot triggers

FAQ

Questions about Send Transactional Email.

What does the Send Transactional Email action do in Brevo?

Sends a one-shot transactional email — pass either HTML body or reference a Brevo template ID with merge parameters. For "password reset, order confirmation, receipt" workflows where each email is unique to the recipient and the moment.

What inputs does Send Transactional Email require?

Required: To Email, Sender Email, Subject, HTML Content. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Brevo returns an error?

The run history shows the failed step with its input and the error message Brevo returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Send Transactional Email support batch operations?

Run Send Transactional Email inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Brevo's rate limits.

More actions