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_CONNECTIONSwith toolkitbrevo - •Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - •Call
RUBE_MANAGE_CONNECTIONSwith toolkitbrevo - •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: Settrueto 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 withhtmlUrl) - •
htmlUrl: URL to HTML content - •
sender: Sender object withname,email, orid - •
recipients: Object withlistIdsandexclusionListIds - •
scheduledAt: Scheduled send time (YYYY-MM-DDTHH:mm:ss.SSSZ)
Pitfalls:
- •
startDateandendDateare mutually required; provide both or neither - •Date filters only work when
statusis not passed or set to 'sent' - •
htmlContentandhtmlUrlare mutually exclusive - •Campaign
senderemail must be a verified sender in Brevo - •A/B testing fields (
subjectA,subjectB,splitRule,winnerCriteria) requireabTesting: true - •
scheduledAtuses 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 orhtmlUrl) - •
sender: Sender object withnameandemail, orid(required for creation) - •
replyTo: Reply-to email address - •
isActive: Activate or deactivate the template - •
tag: Category tag for the template
Pitfalls:
- •When
templateIdis provided, the tool updates; when omitted, it creates - •For creation,
templateName,subject, andsenderare required - •
htmlContentmust be at least 10 characters - •Template personalization uses
{{contact.ATTRIBUTE}}syntax - •Only inactive templates can be deleted
- •
htmlContentandhtmlUrlare 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.idfields 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 totrueto enable A/B testing - •
subjectA: Subject line for variant A - •
subjectB: Subject line for variant B - •