ActionBrevoUpdated June 2026

How do I send a transactional email via Brevo?

Short answer: Drop the "BrevoSend Transactional Email" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
To Email
to_email
stringRequiredRecipient email address
To Name
to_name
stringOptionalRecipient display name
Sender Email
sender_email
stringRequiredMust be a verified sender in your Brevo account
Sender Name
sender_name
stringOptionalSender Name. e.g. "Your Company"
Subject
subject
stringRequiredSubject. Example: Your order has been confirmed
HTML Content
htmlContent
stringRequiredHTML body of the email
Reply-To Email
reply_to_email
stringOptionalEmail 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.

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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Send Transactional Email support batch operations?
Yes. Run Send Transactional Email inside a Loop node to process arrays. Tiny Command handles Brevo's rate limits automatically so you don't have to throttle manually.
More actions

Other Brevo actions.

Action
Add Contact to List
Adds an existing contact to a specific Brevo list. If the contact isn't in the account, this fails — use Create Contact first or the upsert pattern. List membership drives campaign targeting.
Action
Create Contact
Creates or upserts (when updateEnabled=true) a contact with email, attributes, and initial list memberships. The base hook for "form submission → push to Brevo" sync workflows.
Action
Delete Contact
Hard-deletes the contact and history. Irreversible — for GDPR right-to-erasure compliance workflows. For soft removal that preserves engagement history, unsubscribe or move to a suppression list instead.
Action
Get Contact
Returns the contact by email or ID with all attributes and list memberships. The standard lookup for enrichment workflows or for resolving "is this email in Brevo already" before downstream decisions.
Action
List Contacts
Paginated contacts with filters by list, segment, modified date. For sync workflows that mirror Brevo into a warehouse, paginate with the modifiedSince filter to incrementally pull only touched records.
Action
List Brevo Lists
Returns every list in the connected account with name, contact count, folder. Useful for populating list-pickers at workflow setup or for inventorying audience structure.

Send send transactional email from your workflows.

Triggered by anything in the catalog. Free tier available. No credit card.