Update email campaign with the Brevo API

Updates a draft or scheduled email campaign. Only the fields sent change. Setting scheduledAt schedules the sending.

Identifier
brevo_update_email_campaign

The request

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

{
  "customer_toolkit": "<connection UUID>",
  "arguments": {
    "campaignId": 1
  }
}

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
campaignIdintegerYesId of the campaign, from List email campaigns.
namestringNoInternal name of the campaign.
senderobjectNoSender 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. Do not send it together with htmlUrl.
htmlUrlstringNoURL of the HTML body of the email. Do not send it together with htmlContent.
recipientsobjectNoWho receives the campaign: listIds from List contact lists, with optional exclusionListIds. Update listIds only on a campaign created with listIds.
replyTostringNoEmail address that receives the replies.
toFieldstringNoPersonalized To field, for example {FIRSTNAME} {LASTNAME}.
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.

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