Automate Brevo Email Campaigns and Templates

This skill automates Brevo (formerly Sendinblue) email marketing operations through Composio's Brevo toolkit via Rube MCP, covering email campaigns, templates, senders, and A/B testing. Its own rule is to always call RUBE_SEARCH_TOOLS first to get current tool schemas.

Prerequisites are Rube MCP connected with RUBE_SEARCH_TOOLS available, and an active Brevo connection through RUBE_MANAGE_CONNECTIONS with toolkit brevo. Setup means adding https://rube.app/mcp as an MCP server (no API keys needed), verifying RUBE_SEARCH_TOOLS responds, calling RUBE_MANAGE_CONNECTIONS with toolkit brevo, and following the returned auth link if the connection isn't yet ACTIVE.

It documents four core workflows with tool sequences:

• Managing email campaigns: BREVO_LIST_EMAIL_CAMPAIGNS with filters for type, status, a startDate/endDate pair (mutually required, and only effective when status is unset or 'sent'), statistics, limit, offset, and sort; then optionally BREVO_UPDATE_EMAIL_CAMPAIGN by campaign_id, setting name, subject, htmlContent or htmlUrl (mutually exclusive), sender, recipients (listIds and exclusionListIds), and scheduledAt in full ISO 8601 format. A/B testing fields (subjectA, subjectB, splitRule, winnerCriteria) require abTesting: true, and the campaign sender email must already be a verified sender in Brevo.
• Creating and managing email templates: BREVO_GET_ALL_EMAIL_TEMPLATES to list, filtered by templateStatus, limit (up to 1000), offset, and sort; BREVO_CREATE_OR_UPDATE_EMAIL_TEMPLATE, which updates when templateId is given and creates when it's omitted, requiring templateName, subject, and sender for creation, with htmlContent (or htmlUrl, mutually exclusive) at least 10 characters and personalization via {{contact.ATTRIBUTE}} syntax; and BREVO_DELETE_EMAIL_TEMPLATE, which only works on inactive templates.
• Managing senders: BREVO_GET_ALL_SENDERS lists verified sender identities. Sender verification itself happens in the Brevo web interface, not via API, and verified sender IDs can be reused in a campaign's or template's sender.id field.
• Configuring A/B testing campaigns: BREVO_LIST_EMAIL_CAMPAIGNS to find the target campaign, then BREVO_UPDATE_EMAIL_CAMPAIGN with abTesting: true, subjectA and subjectB, a splitRule percentage (1-99, the share receiving variant A), a winnerCriteria of 'open' or 'click', and a winnerDelay in hours (1-168) before the winner is sent to the rest; this only works with the 'classic' campaign type.

It documents a campaign lifecycle pattern (create as draft, set recipients, configure content, optionally schedule, send or schedule via the Brevo UI or an API update setting scheduledAt), pagination via limit and offset (default limit 50, max 100 for campaigns and 1000 for templates, checking count in the response for the total available), and template personalization tags for first name, last name, a custom attribute, the mirror link, and the unsubscribe link. Known pitfalls include all dates using ISO 8601 with milliseconds and timezone, unverified senders causing campaign or template failures (check with GET_ALL_SENDERS first), rate limits requiring backoff on 429 responses with template operations more tightly limited than reads, and response data sometimes nested under data or data.data with numeric campaign and template IDs.

Use it when a user wants to list, review, or update email campaigns, create or manage email templates, view verified senders, or set up or modify A/B testing on a campaign in Brevo.

Do not use it to verify a new sender identity, since that step must be done through the Brevo web interface and cannot be done via this API.

Inputs are the Brevo campaign or template identifiers, content (subject, HTML body or URL), sender details, recipient lists, and A/B test parameters. Outputs are campaign and template lists and update confirmations, verified sender lists, and A/B test configuration results.

It is for marketers and growth or lifecycle teams who want to drive Brevo email campaign and template management, including A/B testing, programmatically through an MCP-connected agent instead of the Brevo UI.