brevo.sendEmail sends inline content or an active template. Message versions let recipients use different content, parameters, or templates in one request.
Example
Inputs
For inline email, providesender, subject, to, and at least one of text, markdown, or html. Automate.ax preserves supplied plain-text and HTML bodies. Markdown generates either missing alternative. Otherwise, HTML generates plain text, and plain text generates HTML. Use a sender in the form { email, name? } or { id, name? } that you’ve registered in Brevo. With templateId, the template can supply sender, subject, and content. to, cc, and bcc contain { email, name?, contactPixelTrackingConsent? }. Set contactPixelTrackingConsent when the recipient has explicitly granted or denied identified pixel tracking. Provide to unless messageVersions is present.
Optional fields include params: Record<string, JSONValue>, replyTo, custom string/number headers, tags, RFC 3339 scheduledAt, UUID batchId, and attachments. An attachment is { content: string; name: string } with base64 content or { url: string; name?: string } with a public URL.
Each message version requires 1–99 to recipients and can override bcc, cc, text, markdown, html, params, replyTo, subject, and templateId. Body overrides use the same derivation rules. All versions together support at most 2,000 recipients. Second argument { account } selects the Brevo binding.
Output
Returns{ messageId: string } for a normal send or { messageIds: string[] } for a multi-version send. Use those IDs with Get email content or event filters.
Brevo charges the connected account per recipient, including version recipients. Scheduling doesn’t bypass plan limits. Success means Brevo accepted the request, not that the recipient mail server delivered it. Use the delivery triggers to track delivery.