Create email campaign with the Brevo API

Creates an email campaign as a draft and returns its id. Send the content in exactly one of htmlContent, htmlUrl or templateId. Setting scheduledAt schedules the sending, and then recipients are required.

Identifier
brevo_create_email_campaign

The request

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

{
  "customer_toolkit": "<connection UUID>",
  "arguments": {
    "name": "<name>",
    "sender": {}
  }
}

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
namestringYesInternal name of the campaign.
senderobjectYesSender of the campaign: email and name, or the id of a sender of the account. Never email and id together.
subjectstringNoSubject of the email.
previewTextstringNoPreview text shown after the subject in the inbox.
htmlContentstringNoBody of the email as HTML, more than 10 characters and under 1 MB.
htmlUrlstringNoURL of the HTML body of the email.
templateIdintegerNoId of an active email template, shown next to its name in the templates list of Brevo. Its content is copied into the campaign.
recipientsobjectNoWho receives the campaign: listIds from List contact lists, with optional exclusionListIds.
replyTostringNoEmail address that receives the replies.
toFieldstringNoPersonalized To field, for example {FIRSTNAME} {LASTNAME}. The attributes must exist in the account.
scheduledAtstringNoWhen to send, with the time zone, for example 2026-06-01T12:30:00-03:00. It schedules the sending.
tagstringNoTag of the campaign.
utmCampaignstringNoutm_campaign value of the links, letters, digits and spaces only. The default is the campaign name.

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_create_email_campaign. 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.