Brevo Automation via Rube MCP
Automate Brevo (formerly Sendinblue) email marketing operations through Composio's Brevo toolkit via Rube MCP.
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Brevo connection via
RUBE_MANAGE_CONNECTIONS with toolkit brevo
- Always call
RUBE_SEARCH_TOOLS first to get current tool schemas
Setup
Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLS responds
- Call
RUBE_MANAGE_CONNECTIONS with toolkit brevo
- If connection is not ACTIVE, follow the returned auth link to complete Brevo authentication
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. Manage Email Campaigns
When to use: User wants to list, review, or update email campaigns
Tool sequence:
BREVO_LIST_EMAIL_CAMPAIGNS - List all campaigns with filters [Required]
BREVO_UPDATE_EMAIL_CAMPAIGN - Update campaign content or settings [Optional]
Key parameters for listing:
type: Campaign type ('classic' or 'trigger')
status: Campaign status ('suspended', 'archive', 'sent', 'queued', 'draft', 'inProcess', 'inReview')
startDate/endDate: Date range filter (YYYY-MM-DDTHH:mm:ss.SSSZ format)
statistics: Stats type to include ('globalStats', 'linksStats', 'statsByDomain')
limit: Results per page (max 100, default 50)
offset: Pagination offset
sort: Sort order ('asc' or 'desc')
excludeHtmlContent: Set true to reduce response size
Key parameters for update:
campaign_id: Numeric campaign ID (required)
name: Campaign name
subject: Email subject line
htmlContent: HTML email body (mutually exclusive with htmlUrl)
htmlUrl: URL to HTML content
sender: Sender object with name, email, or id
recipients: Object with listIds and exclusionListIds
scheduledAt: Scheduled send time (YYYY-MM-DDTHH:mm:ss.SSSZ)
Pitfalls:
startDate and endDate are mutually required; provide both or neither
- Date filters only work when
status is not passed or set to 'sent'
htmlContent and htmlUrl are mutually exclusive
- Campaign
sender email must be a verified sender in Brevo
- A/B testing fields (
subjectA, subjectB, splitRule, winnerCriteria) require abTesting: true
scheduledAt uses full ISO 8601 format with timezone
2. Create and Manage Email Templates
When to use: User wants to create, edit, list, or delete email templates
Tool sequence:
BREVO_GET_ALL_EMAIL_TEMPLATES - List all templates [Required]
BREVO_CREATE_OR_UPDATE_EMAIL_TEMPLATE - Create a new template or update existing [Required]
BREVO_DELETE_EMAIL_TEMPLATE - Delete an inactive template [Optional]
Key parameters for listing:
templateStatus: Filter active (true) or inactive (false) templates
limit: Results per page (max 1000, default 50)
offset: Pagination offset
sort: Sort order ('asc' or 'desc')
Key parameters for create/update:
templateId: Include to update; omit to create new
templateName: Template display name (required for creation)
subject: Email subject line (required for creation)
htmlContent: HTML template body (min 10 characters; use this or htmlUrl)
sender: Sender object with name and email, or id (required for creation)
replyTo: Reply-to email address
isActive: Activate or deactivate the template
tag: Category tag for the template
Pitfalls:
- When
templateId is provided, the tool updates; when omitted, it creates
- For creation,
templateName, subject, and sender are required
htmlContent must be at least 10 characters
- Template personalization uses
{{contact.ATTRIBUTE}} syntax
- Only inactive templates can be deleted
htmlContent and htmlUrl are mutually exclusive
3. Manage Senders
When to use: User wants to view authorized sender identities
Tool sequence:
BREVO_GET_ALL_SENDERS - List all verified senders [Required]
Key parameters: (none required)
Pitfalls:
- Senders must be verified before they can be used in campaigns or templates
- Sender verification is done through the Brevo web interface, not via API
- Sender IDs can be used in
sender.id fields for campaigns and templates
4. Configure A/B Testing Campaigns
When to use: User wants to set up or modify A/B test settings on a campaign
Tool sequence:
BREVO_LIST_EMAIL_CAMPAIGNS - Find the target campaign [Prerequisite]
BREVO_UPDATE_EMAIL_CAMPAIGN - Configure A/B test settings [Required]
Key parameters:
campaign_id: Campaign to configure
abTesting: Set to true to enable A/B testing
subjectA: Subject line for variant A
subjectB: Subject line for variant B
splitRule: Percentage split for the test (1-99)
winnerCriteria: 'open' or 'click' for determining the winner
winnerDelay: Hours to wait before selecting winner (1-168)
Pitfalls:
- A/B testing must be enabled (
abTesting: true) before setting variant fields
splitRule is the percentage of contacts that receive variant A
winnerDelay defines how long to test before sending the winner to remaining contacts
- Only works with 'classic' campaign type
Common Patterns
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)
Pagination
- Use
limit (page size) and offset (starting index)
- Default limit is 50; max varies by endpoint (100 for campaigns, 1000 for templates)
- Increment
offset by limit each page
- Check
count in response to determine total available
Template Personalization
- First name: {{contact.FIRSTNAME}}
- Last name: {{contact.LASTNAME}}
- Custom attribute: {{contact.CUSTOM_ATTRIBUTE}}
- Mirror link: {{mirror}}
- Unsubscribe link: {{unsubscribe}}
Known Pitfalls
Date Formats:
- All dates use ISO 8601 with milliseconds: YYYY-MM-DDTHH:mm:ss.SSSZ
- Pass timezone in the date-time format for accurate results
startDate and endDate must be used together
Sender Verification:
- All sender emails must be verified in Brevo before use
- Unverified senders cause campaign creation/update failures
- Use GET_ALL_SENDERS to check available verified senders
Rate Limits:
- Brevo API has rate limits per account plan
- Implement backoff on 429 responses
- Template operations have lower limits than read operations
Response Parsing:
- Response data may be nested under
data or data.data
- Parse defensively with fallback patterns
- Campaign and template IDs are numeric integers
Quick Reference
| Task |
Tool Slug |
Key Params |
| List campaigns |
BREVO_LIST_EMAIL_CAMPAIGNS |
type, status, limit, offset |
| Update campaign |
BREVO_UPDATE_EMAIL_CAMPAIGN |
campaign_id, subject, htmlContent |
| List templates |
BREVO_GET_ALL_EMAIL_TEMPLATES |
templateStatus, limit, offset |
| Create template |
BREVO_CREATE_OR_UPDATE_EMAIL_TEMPLATE |
templateName, subject, htmlContent, sender |
| Update template |
BREVO_CREATE_OR_UPDATE_EMAIL_TEMPLATE |
templateId, htmlContent |
| Delete template |
BREVO_DELETE_EMAIL_TEMPLATE |
templateId |
| List senders |
BREVO_GET_ALL_SENDERS |
(none) |
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for enprojectnment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
1---2name: brevo-automation3description: "Automate Brevo (formerly Sendinblue) email marketing operations through Composio's Brevo toolkit via Rube MCP."4risk: critical5source: community6date_added: "2026-02-27"7metadata:8 source: https://skillmd.com/skills/phoroth/brevo-automation9---1011# Brevo Automation via Rube MCP1213Automate Brevo (formerly Sendinblue) email marketing operations through Composio's Brevo toolkit via Rube MCP.1415## Prerequisites1617- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)18- Active Brevo connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `brevo`19- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas2021## Setup2223**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.2425261. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds272. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `brevo`283. If connection is not ACTIVE, follow the returned auth link to complete Brevo authentication294. Confirm connection status shows ACTIVE before running any workflows3031## Core Workflows3233### 1. Manage Email Campaigns3435**When to use**: User wants to list, review, or update email campaigns3637**Tool sequence**:381. `BREVO_LIST_EMAIL_CAMPAIGNS` - List all campaigns with filters [Required]392. `BREVO_UPDATE_EMAIL_CAMPAIGN` - Update campaign content or settings [Optional]4041**Key parameters for listing**:42- `type`: Campaign type ('classic' or 'trigger')43- `status`: Campaign status ('suspended', 'archive', 'sent', 'queued', 'draft', 'inProcess', 'inReview')44- `startDate`/`endDate`: Date range filter (YYYY-MM-DDTHH:mm:ss.SSSZ format)45- `statistics`: Stats type to include ('globalStats', 'linksStats', 'statsByDomain')46- `limit`: Results per page (max 100, default 50)47- `offset`: Pagination offset48- `sort`: Sort order ('asc' or 'desc')49- `excludeHtmlContent`: Set `true` to reduce response size5051**Key parameters for update**:52- `campaign_id`: Numeric campaign ID (required)53- `name`: Campaign name54- `subject`: Email subject line55- `htmlContent`: HTML email body (mutually exclusive with `htmlUrl`)56- `htmlUrl`: URL to HTML content57- `sender`: Sender object with `name`, `email`, or `id`58- `recipients`: Object with `listIds` and `exclusionListIds`59- `scheduledAt`: Scheduled send time (YYYY-MM-DDTHH:mm:ss.SSSZ)6061**Pitfalls**:62- `startDate` and `endDate` are mutually required; provide both or neither63- Date filters only work when `status` is not passed or set to 'sent'64- `htmlContent` and `htmlUrl` are mutually exclusive65- Campaign `sender` email must be a verified sender in Brevo66- A/B testing fields (`subjectA`, `subjectB`, `splitRule`, `winnerCriteria`) require `abTesting: true`67- `scheduledAt` uses full ISO 8601 format with timezone6869### 2. Create and Manage Email Templates7071**When to use**: User wants to create, edit, list, or delete email templates7273**Tool sequence**:741. `BREVO_GET_ALL_EMAIL_TEMPLATES` - List all templates [Required]752. `BREVO_CREATE_OR_UPDATE_EMAIL_TEMPLATE` - Create a new template or update existing [Required]763. `BREVO_DELETE_EMAIL_TEMPLATE` - Delete an inactive template [Optional]7778**Key parameters for listing**:79- `templateStatus`: Filter active (`true`) or inactive (`false`) templates80- `limit`: Results per page (max 1000, default 50)81- `offset`: Pagination offset82- `sort`: Sort order ('asc' or 'desc')8384**Key parameters for create/update**:85- `templateId`: Include to update; omit to create new86- `templateName`: Template display name (required for creation)87- `subject`: Email subject line (required for creation)88- `htmlContent`: HTML template body (min 10 characters; use this or `htmlUrl`)89- `sender`: Sender object with `name` and `email`, or `id` (required for creation)90- `replyTo`: Reply-to email address91- `isActive`: Activate or deactivate the template92- `tag`: Category tag for the template9394**Pitfalls**:95- When `templateId` is provided, the tool updates; when omitted, it creates96- For creation, `templateName`, `subject`, and `sender` are required97- `htmlContent` must be at least 10 characters98- Template personalization uses `{{contact.ATTRIBUTE}}` syntax99- Only inactive templates can be deleted100- `htmlContent` and `htmlUrl` are mutually exclusive101102### 3. Manage Senders103104**When to use**: User wants to view authorized sender identities105106**Tool sequence**:1071. `BREVO_GET_ALL_SENDERS` - List all verified senders [Required]108109**Key parameters**: (none required)110111**Pitfalls**:112- Senders must be verified before they can be used in campaigns or templates113- Sender verification is done through the Brevo web interface, not via API114- Sender IDs can be used in `sender.id` fields for campaigns and templates115116### 4. Configure A/B Testing Campaigns117118**When to use**: User wants to set up or modify A/B test settings on a campaign119120**Tool sequence**:1211. `BREVO_LIST_EMAIL_CAMPAIGNS` - Find the target campaign [Prerequisite]1222. `BREVO_UPDATE_EMAIL_CAMPAIGN` - Configure A/B test settings [Required]123124**Key parameters**:125- `campaign_id`: Campaign to configure126- `abTesting`: Set to `true` to enable A/B testing127- `subjectA`: Subject line for variant A128- `subjectB`: Subject line for variant B129- `splitRule`: Percentage split for the test (1-99)130- `winnerCriteria`: 'open' or 'click' for determining the winner131- `winnerDelay`: Hours to wait before selecting winner (1-168)132133**Pitfalls**:134- A/B testing must be enabled (`abTesting: true`) before setting variant fields135- `splitRule` is the percentage of contacts that receive variant A136- `winnerDelay` defines how long to test before sending the winner to remaining contacts137- Only works with 'classic' campaign type138139## Common Patterns140141### Campaign Lifecycle142143```1441. Create campaign (status: draft)1452. Set recipients (listIds)1463. Configure content (htmlContent or htmlUrl)1474. Optionally schedule (scheduledAt)1485. Send or schedule via Brevo UI (API update can set scheduledAt)149```150151### Pagination152153- Use `limit` (page size) and `offset` (starting index)154- Default limit is 50; max varies by endpoint (100 for campaigns, 1000 for templates)155- Increment `offset` by `limit` each page156- Check `count` in response to determine total available157158### Template Personalization159160```161- First name: {{contact.FIRSTNAME}}162- Last name: {{contact.LASTNAME}}163- Custom attribute: {{contact.CUSTOM_ATTRIBUTE}}164- Mirror link: {{mirror}}165- Unsubscribe link: {{unsubscribe}}166```167168## Known Pitfalls169170**Date Formats**:171- All dates use ISO 8601 with milliseconds: YYYY-MM-DDTHH:mm:ss.SSSZ172- Pass timezone in the date-time format for accurate results173- `startDate` and `endDate` must be used together174175**Sender Verification**:176- All sender emails must be verified in Brevo before use177- Unverified senders cause campaign creation/update failures178- Use GET_ALL_SENDERS to check available verified senders179180**Rate Limits**:181- Brevo API has rate limits per account plan182- Implement backoff on 429 responses183- Template operations have lower limits than read operations184185**Response Parsing**:186- Response data may be nested under `data` or `data.data`187- Parse defensively with fallback patterns188- Campaign and template IDs are numeric integers189190## Quick Reference191192| Task | Tool Slug | Key Params |193|------|-----------|------------|194| List campaigns | BREVO_LIST_EMAIL_CAMPAIGNS | type, status, limit, offset |195| Update campaign | BREVO_UPDATE_EMAIL_CAMPAIGN | campaign_id, subject, htmlContent |196| List templates | BREVO_GET_ALL_EMAIL_TEMPLATES | templateStatus, limit, offset |197| Create template | BREVO_CREATE_OR_UPDATE_EMAIL_TEMPLATE | templateName, subject, htmlContent, sender |198| Update template | BREVO_CREATE_OR_UPDATE_EMAIL_TEMPLATE | templateId, htmlContent |199| Delete template | BREVO_DELETE_EMAIL_TEMPLATE | templateId |200| List senders | BREVO_GET_ALL_SENDERS | (none) |201202## When to Use203This skill is applicable to execute the workflow or actions described in the overview.204205## Limitations206- Use this skill only when the task clearly matches the scope described above.207- Do not treat the output as a substitute for enprojectnment-specific validation, testing, or expert review.208- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.