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) |
1---
2name: brevo-automation
3description: "Automate Brevo (Sendinblue) tasks via Rube MCP (Composio): manage email campaigns, create/edit templates, track senders, and monitor campaign performance. Always search tools first for current schemas."
4requires:
5 mcp: [rube]
6metadata:
7 source: https://skillmd.com/skills/aaaaqwq/brevo-automation
8---
9
10# Brevo Automation via Rube MCP
11
12Automate Brevo (formerly Sendinblue) email marketing operations through Composio's Brevo toolkit via Rube MCP.
13
14## Prerequisites
15
16- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
17- Active Brevo connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `brevo`
18- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
19
20## Setup
21
22**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.
23
24
251. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
262. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `brevo`
273. If connection is not ACTIVE, follow the returned auth link to complete Brevo authentication
284. Confirm connection status shows ACTIVE before running any workflows
29
30## Core Workflows
31
32### 1. Manage Email Campaigns
33
34**When to use**: User wants to list, review, or update email campaigns
35
36**Tool sequence**:
371. `BREVO_LIST_EMAIL_CAMPAIGNS` - List all campaigns with filters [Required]
382. `BREVO_UPDATE_EMAIL_CAMPAIGN` - Update campaign content or settings [Optional]
39
40**Key parameters for listing**:
41- `type`: Campaign type ('classic' or 'trigger')
42- `status`: Campaign status ('suspended', 'archive', 'sent', 'queued', 'draft', 'inProcess', 'inReview')
43- `startDate`/`endDate`: Date range filter (YYYY-MM-DDTHH:mm:ss.SSSZ format)
44- `statistics`: Stats type to include ('globalStats', 'linksStats', 'statsByDomain')
45- `limit`: Results per page (max 100, default 50)
46- `offset`: Pagination offset
47- `sort`: Sort order ('asc' or 'desc')
48- `excludeHtmlContent`: Set `true` to reduce response size
49
50**Key parameters for update**:
51- `campaign_id`: Numeric campaign ID (required)
52- `name`: Campaign name
53- `subject`: Email subject line
54- `htmlContent`: HTML email body (mutually exclusive with `htmlUrl`)
55- `htmlUrl`: URL to HTML content
56- `sender`: Sender object with `name`, `email`, or `id`
57- `recipients`: Object with `listIds` and `exclusionListIds`
58- `scheduledAt`: Scheduled send time (YYYY-MM-DDTHH:mm:ss.SSSZ)
59
60**Pitfalls**:
61- `startDate` and `endDate` are mutually required; provide both or neither
62- Date filters only work when `status` is not passed or set to 'sent'
63- `htmlContent` and `htmlUrl` are mutually exclusive
64- Campaign `sender` email must be a verified sender in Brevo
65- A/B testing fields (`subjectA`, `subjectB`, `splitRule`, `winnerCriteria`) require `abTesting: true`
66- `scheduledAt` uses full ISO 8601 format with timezone
67
68### 2. Create and Manage Email Templates
69
70**When to use**: User wants to create, edit, list, or delete email templates
71
72**Tool sequence**:
731. `BREVO_GET_ALL_EMAIL_TEMPLATES` - List all templates [Required]
742. `BREVO_CREATE_OR_UPDATE_EMAIL_TEMPLATE` - Create a new template or update existing [Required]
753. `BREVO_DELETE_EMAIL_TEMPLATE` - Delete an inactive template [Optional]
76
77**Key parameters for listing**:
78- `templateStatus`: Filter active (`true`) or inactive (`false`) templates
79- `limit`: Results per page (max 1000, default 50)
80- `offset`: Pagination offset
81- `sort`: Sort order ('asc' or 'desc')
82
83**Key parameters for create/update**:
84- `templateId`: Include to update; omit to create new
85- `templateName`: Template display name (required for creation)
86- `subject`: Email subject line (required for creation)
87- `htmlContent`: HTML template body (min 10 characters; use this or `htmlUrl`)
88- `sender`: Sender object with `name` and `email`, or `id` (required for creation)
89- `replyTo`: Reply-to email address
90- `isActive`: Activate or deactivate the template
91- `tag`: Category tag for the template
92
93**Pitfalls**:
94- When `templateId` is provided, the tool updates; when omitted, it creates
95- For creation, `templateName`, `subject`, and `sender` are required
96- `htmlContent` must be at least 10 characters
97- Template personalization uses `{{contact.ATTRIBUTE}}` syntax
98- Only inactive templates can be deleted
99- `htmlContent` and `htmlUrl` are mutually exclusive
100
101### 3. Manage Senders
102
103**When to use**: User wants to view authorized sender identities
104
105**Tool sequence**:
1061. `BREVO_GET_ALL_SENDERS` - List all verified senders [Required]
107
108**Key parameters**: (none required)
109
110**Pitfalls**:
111- Senders must be verified before they can be used in campaigns or templates
112- Sender verification is done through the Brevo web interface, not via API
113- Sender IDs can be used in `sender.id` fields for campaigns and templates
114
115### 4. Configure A/B Testing Campaigns
116
117**When to use**: User wants to set up or modify A/B test settings on a campaign
118
119**Tool sequence**:
1201. `BREVO_LIST_EMAIL_CAMPAIGNS` - Find the target campaign [Prerequisite]
1212. `BREVO_UPDATE_EMAIL_CAMPAIGN` - Configure A/B test settings [Required]
122
123**Key parameters**:
124- `campaign_id`: Campaign to configure
125- `abTesting`: Set to `true` to enable A/B testing
126- `subjectA`: Subject line for variant A
127- `subjectB`: Subject line for variant B
128- `splitRule`: Percentage split for the test (1-99)
129- `winnerCriteria`: 'open' or 'click' for determining the winner
130- `winnerDelay`: Hours to wait before selecting winner (1-168)
131
132**Pitfalls**:
133- A/B testing must be enabled (`abTesting: true`) before setting variant fields
134- `splitRule` is the percentage of contacts that receive variant A
135- `winnerDelay` defines how long to test before sending the winner to remaining contacts
136- Only works with 'classic' campaign type
137
138## Common Patterns
139
140### Campaign Lifecycle
141
142```
1431. Create campaign (status: draft)
1442. Set recipients (listIds)
1453. Configure content (htmlContent or htmlUrl)
1464. Optionally schedule (scheduledAt)
1475. Send or schedule via Brevo UI (API update can set scheduledAt)
148```
149
150### Pagination
151
152- Use `limit` (page size) and `offset` (starting index)
153- Default limit is 50; max varies by endpoint (100 for campaigns, 1000 for templates)
154- Increment `offset` by `limit` each page
155- Check `count` in response to determine total available
156
157### Template Personalization
158
159```
160- First name: {{contact.FIRSTNAME}}
161- Last name: {{contact.LASTNAME}}
162- Custom attribute: {{contact.CUSTOM_ATTRIBUTE}}
163- Mirror link: {{mirror}}
164- Unsubscribe link: {{unsubscribe}}
165```
166
167## Known Pitfalls
168
169**Date Formats**:
170- All dates use ISO 8601 with milliseconds: YYYY-MM-DDTHH:mm:ss.SSSZ
171- Pass timezone in the date-time format for accurate results
172- `startDate` and `endDate` must be used together
173
174**Sender Verification**:
175- All sender emails must be verified in Brevo before use
176- Unverified senders cause campaign creation/update failures
177- Use GET_ALL_SENDERS to check available verified senders
178
179**Rate Limits**:
180- Brevo API has rate limits per account plan
181- Implement backoff on 429 responses
182- Template operations have lower limits than read operations
183
184**Response Parsing**:
185- Response data may be nested under `data` or `data.data`
186- Parse defensively with fallback patterns
187- Campaign and template IDs are numeric integers
188
189## Quick Reference
190
191| Task | Tool Slug | Key Params |
192|------|-----------|------------|
193| List campaigns | BREVO_LIST_EMAIL_CAMPAIGNS | type, status, limit, offset |
194| Update campaign | BREVO_UPDATE_EMAIL_CAMPAIGN | campaign_id, subject, htmlContent |
195| List templates | BREVO_GET_ALL_EMAIL_TEMPLATES | templateStatus, limit, offset |
196| Create template | BREVO_CREATE_OR_UPDATE_EMAIL_TEMPLATE | templateName, subject, htmlContent, sender |
197| Update template | BREVO_CREATE_OR_UPDATE_EMAIL_TEMPLATE | templateId, htmlContent |
198| Delete template | BREVO_DELETE_EMAIL_TEMPLATE | templateId |
199| List senders | BREVO_GET_ALL_SENDERS | (none) |