Automate Brevo Email Campaigns and Templates

This is a skill for automating Brevo (formerly Sendinblue) email marketing operations through Composio's Brevo toolkit, accessed via Rube MCP (https://rube.app/mcp, added as an MCP server with no API keys needed on the client side - the toolkit still requires an active Brevo connection authenticated through RUBE_MANAGE_CONNECTIONS). It covers four core workflows: managing email campaigns (BREVO_LIST_EMAIL_CAMPAIGNS and BREVO_UPDATE_EMAIL_CAMPAIGN, with filters for type, status, and date range), creating and managing email templates (list, create/update, delete, with {{contact.ATTRIBUTE}} personalization syntax), managing verified senders (BREVO_GET_ALL_SENDERS, since sender verification only happens through Brevo's own web interface, not the API), and configuring A/B testing campaigns (abTesting: true plus subjectA/subjectB/splitRule/winnerCriteria, classic campaigns only). A representative campaign lifecycle:

1. Create campaign (status: draft)
2. Set recipients (listIds)
3. Configure content (htmlContent or htmlUrl)
4. Optionally schedule (scheduledAt)
5. Send or schedule via Brevo UI (API update can set scheduledAt)

Use this skill when automating Brevo campaign management, template creation, sender verification checks, or A/B test configuration through Rube MCP once the Brevo connection is confirmed ACTIVE. Always call RUBE_SEARCH_TOOLS first to get current tool schemas rather than assuming parameter names. It is not the right tool if the Brevo connection isn't active yet - the setup flow (verify RUBE_SEARCH_TOOLS, call RUBE_MANAGE_CONNECTIONS for the brevo toolkit, complete the returned auth link if not ACTIVE) must complete before any workflow runs.

Input is campaign or template parameters - subject lines, HTML content (mutually exclusive with an HTML URL), sender identity, recipient list IDs, and ISO 8601 scheduling timestamps; output is created or updated campaigns and templates, verified-sender listings, and A/B test configurations. Known data-shape pitfalls are called out explicitly: startDate and endDate must be passed together or not at all, response data may be nested under data or data.data, campaign and template IDs are numeric integers, and only inactive templates can be deleted. Pagination uses limit/offset, defaulting to 50 results per page (max 100 for campaigns, 1000 for templates), incrementing offset by limit each page.

Teams automating Brevo email marketing workflows - campaign management, template creation, A/B testing - through an MCP-connected agent, who need the specific tool sequences, parameter formats, and known pitfalls such as mutually exclusive fields and sender-verification requirements rather than guessing at the API surface. Template personalization uses {{contact.FIRSTNAME}}-style tokens plus reserved {{mirror}} and {{unsubscribe}} links, and rate limits apply per account plan with template operations generally more restricted than read operations, so batch template work should back off on repeated 429 responses.