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
| Parameter | Type | Required | Description |
|---|---|---|---|
| campaignId | integer | Yes | Id of the campaign, from List email campaigns. |
| name | string | No | Internal name of the campaign. |
| sender | object | No | Sender of the campaign: email and name, or the id of a sender of the account. Never email and id together. |
| subject | string | No | Subject of the email. |
| previewText | string | No | Preview text shown after the subject in the inbox. |
| htmlContent | string | No | Body of the email as HTML. Do not send it together with htmlUrl. |
| htmlUrl | string | No | URL of the HTML body of the email. Do not send it together with htmlContent. |
| recipients | object | No | Who receives the campaign: listIds from List contact lists, with optional exclusionListIds. Update listIds only on a campaign created with listIds. |
| replyTo | string | No | Email address that receives the replies. |
| toField | string | No | Personalized To field, for example {FIRSTNAME} {LASTNAME}. |
| scheduledAt | string | No | When to send, with the time zone, for example 2026-06-01T12:30:00-03:00. It schedules the sending. |
| tag | string | No | Tag of the campaign. |
| utmCampaign | string | No | utm_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.
Other Brevo tools
- List contactsGETLists the contacts, newest first by default, optionally narrowed by list, date or attribute. The response has contacts and count; page with limit and offset.
- Get contactGETReturns one contact with its attributes, lists and the campaign statistics of the last 90 days.
- Create contactPOSTCreates a contact. Send email, or the SMS attribute, or ext_id. With updateEnabled set to true, an existing contact with the same identifier is updated instead of failing.
- Update contactPUTUpdates a contact. Only the fields sent change: listIds adds the contact to lists and unlinkListIds removes it from lists.
- List contact listsGETLists the contact lists with their id, name, folderId and unique subscribers. The response has lists and count; page with limit and offset.
- Create contact listPOSTCreates an empty contact list in a folder and returns its id.
- List email campaignsGETLists the email campaigns, newest first by default. The response has campaigns and count; page with limit and offset. Statistics come back only when statistics is sent.
- Get email campaignGETReturns one email campaign with its settings, recipients and report statistics.
See Connect applied to your product.
Try it for 15 days with no card, or walk our team through your use case.
