Send transactional email with the Brevo API

Sends a transactional email to the addresses in to, right away or at scheduledAt, and returns its messageId. Send sender, subject and htmlContent or textContent, or a templateId, whose sender and subject apply unless sent.

Identifier
brevo_send_transactional_email

The request

POST https://connect.reportei.com/api/tools/brevo_send_transactional_email/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json

{
  "customer_toolkit": "<connection UUID>",
  "arguments": {
    "to": []
  }
}

Your system sends your customer's connection id and the tool arguments. The headers are the same as the rest of the Connect API: your product's token and your customer's token.

Parameters

ParameterTypeRequiredDescription
toarrayYesRecipients of the email.
senderobjectNoSender: email and name, or the id of a sender of the account. Required without templateId.
subjectstringNoSubject of the email. Required without templateId.
htmlContentstringNoBody of the email as HTML. Required without templateId.
textContentstringNoPlain text body of the email. Ignored with templateId.
templateIdintegerNoId of a transactional template, shown next to its name in the templates list of Brevo.
paramsobjectNoValues for the variables of the template, as key and value.
ccarrayNoRecipients in copy.
bccarrayNoRecipients in blind copy.
replyToobjectNoAddress that receives the replies.
tagsarrayNoTags to categorize the email.
scheduledAtstringNoWhen to send, with the time zone. Scheduled emails may go out up to 5 minutes late.

Supported connections

Your customer connects their Brevo account once, with one of the modes below. The same connection serves every tool of the toolkit.

API key

Your customer pastes the app's key on a Connect screen, or your system sends the key with POST /api/customer-toolkits, with no screen.

The response

On success, Connect preserves the app's response status and body. HTTP errors returned by the app use the {error, api_error} envelope; authentication or validation can fail before execution. The X-Toolkit-Execution-Id header identifies the recorded execution, available at GET /api/tools/executions/{uuid}.

Ready for AI agents

This tool's input is a JSON Schema, available at GET /api/tools/brevo_send_transactional_email. It becomes your agent's tool definition with no conversion.

See Connect applied to your product.

Try it for 15 days with no card, or walk our team through your use case.