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