Menu
Mattering Automations connector

A Brevo MCP for email marketing workflows that reach past Brevo

Connect one API key and contacts, lists, email and SMS campaigns, transactional sends, templates, delivery statistics, and webhooks become workflow steps. A signup can become a contact on the right list with a welcome email already sent, an AI agent can assemble a campaign as a draft and wait for a human before anything goes out, and the reporting lands next to your tasks and databases instead of in another dashboard.

50 ready-made nodes One credential to connect Works with Claude, ChatGPT, and Matter

What the Brevo MCP connector does

The Brevo connector for Mattering Automations is 50 nodes across the Brevo v3 REST API: contacts with attributes, lists, and folders, background imports with process polling, email campaigns from draft to send, SMS campaigns, transactional email with template management, transactional SMS, per-day and aggregated delivery statistics, the transactional event log, verified senders, and webhooks. One API key authenticates all of it.

Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. An agent can look up a contact, file it on a list, send a templated transactional email, and read back the delivery statistics, without anyone opening the Brevo dashboard.

Brevo publishes its own official MCP server at mcp.brevo.com, with MCP tokens generated alongside API keys in the Brevo dashboard, and it is a genuine option when all you want is an assistant talking to Brevo alone. This connector is for the other half of the job, where Brevo is one step among many. On the Mattering canvas the same nodes sit next to every other connector and the platform itself, so a signup webhook can create the contact and then open a follow-up task, a campaign send can wait behind a human approval step, and a nightly statistics sweep can write into a Mattering database. Use whichever fits, or both.

The safety modeling is stated plainly. Of the 50 nodes, 21 read and 29 act, and 13 are flagged destructive: the six send nodes, because a delivered email or SMS cannot be recalled and even test sends reach real inboxes and phones, the six deletes (contact, list, email campaign, email template, SMS campaign, webhook), and Import Contacts, because Brevo's default updateExistingContacts true overwrites existing contacts' attribute values in bulk with no undo. Campaign creation is deliberately calm: Create Email Campaign and Create SMS Campaign produce drafts, and nothing is delivered until a send node fires. Brevo's CRM deals, Conversations, WhatsApp, ecommerce, and sub-account surfaces are separate products and are not part of this connector.

One connection, three surfaces

  • Visual automations. Drag Brevo nodes onto the canvas and wire them to triggers, conditions, and other apps.
  • AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
  • The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.

Every Brevo node, ready to drop on the canvas

50 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.

Read and query nodes 21

Brevo: Get Account

Fetch the Brevo account: owner identity, company, plan and remaining email/SMS credits, and SMTP relay settings. Works with every valid API key, so this is the credential health check to run first in any Brevo automation.

Brevo: Get Contact

Fetch one contact by email, id, SMS number, or EXT_ID: attributes, blacklist flags, list memberships, and campaign engagement history (optionally limited to a date range).

Brevo: Get Email Aggregated Report

One aggregate of transactional email activity for a date window: requests, delivered, bounces, blocked, opens, unique opens, clicks, unique clicks, spam reports, and unsubscribes, plus the range covered. Uses startDate/endDate or days (default 90, maximum 90). For per-day rows use Brevo: Get Email Daily Reports.

Brevo: Get Email Campaign

Fetch one email campaign with its full setup and the campaign report: global and per-list statistics, link clicks, and (single-campaign only) statsByDevice and statsByBrowser.

Brevo: Get Email Daily Reports

Per-day transactional email totals in data.reports[]: each row carries its date plus requests, delivered, hard and soft bounces, blocked, invalid, opens, unique opens, clicks, unique clicks, spam reports, and unsubscribes. Window by startDate/endDate or days (maximum 30). limit caps the number of DAY rows returned and defaults to 10, so raise it to cover the window you ask for.

Brevo: Get Email Events

List individual transactional email events (requests, delivered, opened, clicked, bounces, spam, unsubscribed) with timestamps and message ids. Filter by date range or days back (default 30, maximum 90), recipient, event type, tag, messageId, or template. This is an event log; for per-day totals use Brevo: Get Email Daily Reports.

Brevo: Get Folder Lists

List the contact lists inside one folder.

Brevo: Get List

Fetch one list: name, folder, subscriber counts, and per-campaign statistics for campaigns sent to it (optionally limited to a date range).

Brevo: Get List Contacts

List the contacts belonging to one list, optionally only those modified after a given date-time.

Brevo: Get Process

Poll one background process (from Brevo: Import Contacts) until its status is completed. Import processes report invalid and duplicate counts; exports carry the download URL.

Brevo: Get SMS Campaign

Fetch one SMS campaign with its content, schedule, recipients, and lifetime statistics (sent, delivered, bounces, answered, unsubscriptions).

Brevo: List Attributes

List every contact attribute on the account with its category (normal, transactional, category, calculated, global), type, and any enumeration or multiple-choice options. Attribute names feed contact create/update attributes and the contacts filter.

Brevo: List Contacts

List contacts with their ids, emails, blacklist flags, list memberships, and attributes. Filter by modification or creation date, list, segment, up to 20 contact ids, or an attribute equals-filter. Pages of 50 by default, up to 1000.

Brevo: List Email Campaigns

List email campaigns with status, schedule, sender, recipients, and lifetime statistics. Filter by type, status, or sent-date range (range only when status is sent or unset; the statistics filter trims the stats payload to one block).

Brevo: List Email Templates

List transactional email templates with their COMPLETE content (subject, sender, htmlContent, active flag). The template id feeds sends, campaign creation, and template updates; there is deliberately no single-template get.

Brevo: List Folders

List contact folders with their ids and names. Folders organize lists; the folder id feeds Brevo: Create List. Note Brevo is dropping totalSubscribers and totalBlacklisted on this surface (they default to 0).

Brevo: List Lists

List contact lists with their ids, names, folder, and subscriber counts. The list id from here feeds every list-scoped node and campaign recipient field. Note Brevo is dropping totalSubscribers and totalBlacklisted (they default to 0); use uniqueSubscribers.

Brevo: List Processes

List the account's background processes (contact imports and exports) with their status: queued, in_process, or completed.

Brevo: List SMS Campaigns

List SMS campaigns with status, content, sender, recipients, and lifetime delivery statistics. Filter by status or sent-date range.

Brevo: List Senders

List the account's verified senders with their ids, names, emails, and active flags. Sender emails feed the campaign, template, and transactional send nodes.

Brevo: List Webhooks

List the account's webhooks with their ids, URLs, event subscriptions, and type (transactional, marketing, or inbound). The lister returns the complete webhook object, so there is deliberately no single-webhook get.

Action nodes 29

Brevo: Add Contacts To List

Add existing contacts to a list by email (maximum 150 per request), numeric id, or ext_id. Pass exactly one of the three arrays. For bulk additions prefer Brevo: Import Contacts. Reversible with Brevo: Remove Contacts From List.

Brevo: Create Attribute

Create a contact attribute under a category. Pass type for normal, transactional, or category attributes; value for calculated or global; enumeration for category; multiCategoryOptions for a normal multiple-choice attribute. Returns an empty success body.

Brevo: Create Contact

Create a contact by email, ext_id, or an SMS number passed inside attributes. Attributes use CAPITAL names that already exist on the account. With updateEnabled true an existing contact is updated instead of erroring. Reversible with Brevo: Delete Contact.

Brevo: Create Email Campaign

Create an email campaign as a DRAFT (nothing is sent until Brevo: Send Email Campaign Now, or scheduledAt arrives on a campaign with recipients). Content comes from exactly one of htmlContent, htmlUrl, or templateId. Reversible with Brevo: Delete Email Campaign.

Brevo: Create Email Template

Create a transactional email template. Content is htmlContent or htmlUrl (one required). Reversible with Brevo: Delete Email Template.

Brevo: Create Folder

Create a folder for organizing contact lists.

Brevo: Create List

Create a contact list inside a folder. Reversible with Brevo: Delete List.

Brevo: Create SMS Campaign

Create an SMS campaign as a DRAFT (nothing is sent until Brevo: Send SMS Campaign Now, or scheduledAt arrives). Recipient list ids are mandatory when scheduledAt is set. Reversible with Brevo: Delete SMS Campaign.

Brevo: Create Webhook

Create a webhook that POSTs email or contact events to your URL. Events are required for transactional and marketing types. Reversible with Brevo: Delete Webhook.

Brevo: Delete Contact

DESTRUCTIVE: permanently delete a contact, including its attributes and engagement history. The email address can be re-added later but the history does not come back.

Brevo: Delete Email Campaign

DESTRUCTIVE: delete an email campaign and its report. There is no restore.

Brevo: Delete Email Template

DESTRUCTIVE: delete a transactional email template. Automations and integrations sending by this template id start failing immediately; there is no restore.

Brevo: Delete List

DESTRUCTIVE: delete a list. The contacts themselves survive, but the list, its membership, and its campaign statistics associations are gone for good.

Brevo: Delete SMS Campaign

DESTRUCTIVE: delete an SMS campaign and its statistics. There is no restore.

Brevo: Delete Webhook

DESTRUCTIVE: delete a webhook. Event delivery to its URL stops immediately and undelivered history is not replayed.

Brevo: Import Contacts

DESTRUCTIVE: bulk-import contacts from JSON rows, CSV text, or a hosted file (up to 10MB body). With updateExistingContacts true (Brevo's default) existing contacts' attribute values are overwritten at scale with no undo, and emptyContactsAttributes true erases attributes the import leaves blank. Returns a processId; poll it with Brevo: Get Process.

Brevo: Remove Contacts From List

Remove contacts from a list by email, id, or ext_id, or empty the whole list with all true. The contacts stay on the account and can be re-added.

Brevo: Send Email Campaign Now

DESTRUCTIVE: send the campaign to its ENTIRE recipient list immediately. A sent campaign cannot be recalled. Verify recipients with Brevo: Get Email Campaign and test with Brevo: Send Test Email Campaign first.

Brevo: Send SMS Campaign Now

DESTRUCTIVE: send the SMS campaign to its ENTIRE recipient list immediately, consuming SMS credits. Sent messages cannot be recalled. Test first with Brevo: Send Test SMS Campaign.

Brevo: Send Test Email Campaign

DESTRUCTIVE: send a real test email of the campaign to the given addresses (or the account's whole test list when empty; up to 50 test emails per day). A delivered email cannot be recalled, so this must not run against real addresses in a blind test matrix.

Brevo: Send Test SMS Campaign

DESTRUCTIVE: send a real test SMS of the campaign to one phone number (which must belong to a non-blacklisted contact on the account). A delivered SMS cannot be recalled and consumes a credit.

Brevo: Send Transactional Email

DESTRUCTIVE: send a real transactional email immediately (or at scheduledAt). A delivered email cannot be recalled, so this must never run in a blind test matrix. Content is either htmlContent/textContent with subject and sender, or an active template via templateId with params substitution.

Brevo: Send Transactional SMS

DESTRUCTIVE: send a real SMS to one number immediately, consuming SMS credits. A delivered SMS cannot be recalled, so this must never run in a blind test matrix. Content is inline text or an SMS template via templateId with params.

Brevo: Update Contact

Update a contact: change attribute values (pass EMAIL inside attributes to change the address), add or remove list memberships, or flip blacklist flags. Only fields you fill are sent. Returns an empty success body.

Brevo: Update Email Campaign

Update a draft or scheduled email campaign. Only fields you fill are sent. Returns an empty success body.

Brevo: Update Email Template

Update a transactional email template. Only fields you fill are sent. Returns an empty success body.

Brevo: Update List

Rename a list or move it to another folder. One of the two per request. Returns an empty success body.

Brevo: Update SMS Campaign

Update a draft or scheduled SMS campaign. Only fields you fill are sent. Returns an empty success body.

Brevo: Update Webhook

Update a webhook's URL, event subscriptions, or delivery settings. Only fields you fill are sent. Returns an empty success body.

Connecting Brevo takes one credential

Brevo authenticates every request with a single API key sent as the api-key header. Keys are created in the Brevo dashboard at app.brevo.com under SMTP & API, then API Keys. One key grants the account's entire v3 REST surface; Brevo has no per-key scoping, so treat the key as a master credential and store it only in the connector. Brevo's SMTP relay uses a separate SMTP key type that this connector never needs: it is REST only.

1

Sign in at app.brevo.com, open your account menu, and choose SMTP & API, then the API Keys tab.

2

Click to generate a new API key and name it for its job, for example Mattering Automations, so it can be rotated independently later.

3

Copy the key and store it nowhere except the Mattering credential: a Brevo API key is unscoped and grants the whole account.

4

In Mattering Automations, open Connectors, click Add Connector, choose Brevo, and create a credential with the API key.

5

Click Test Connection. Mattering calls Brevo's account endpoint, which works for every valid key: a successful result returns the plan and remaining credits without echoing the secret, and a 401 Key not found means the key is wrong or was deleted.

6

All 50 Brevo nodes appear in the canvas palette. Run Brevo: List Lists first for list ids and Brevo: List Senders for the verified sender emails that the campaign and transactional send nodes need.

Common uses for the Brevo MCP

Contacts that stay in sync

Brevo: Create Contact with updateEnabled true is the idempotent upsert: a repeat signup updates the existing contact instead of erroring. Brevo: Add Contacts To List files up to 150 contacts per request onto a list, Brevo: Remove Contacts From List reverses it, and for bulk loads Brevo: Import Contacts takes JSON rows, CSV text, or a hosted file up to 10MB and returns a processId to poll with Brevo: Get Process. Import is flagged destructive for a real reason: Brevo's default updateExistingContacts true overwrites existing attribute values at scale with no undo.

Campaign assembly with an approval gate

Brevo: Create Email Campaign produces a draft, and drafts send nothing. A workflow or an AI agent can assemble the campaign, run Brevo: Send Test Email Campaign to put real test emails in the team's inboxes (up to 50 test emails per day), and open an approval task in Mattering Productivity. Only when a person approves does Brevo: Send Email Campaign Now fire, and it is flagged destructive because it delivers to the entire recipient list immediately and cannot be recalled.

Transactional email as a workflow step

Brevo: Send Transactional Email sends from inline HTML or an active template via templateId with params substitution, and returns a messageId for tracing. Templates are managed on the same canvas: Brevo: List Email Templates returns each template's complete content, and the create, update, and delete nodes keep them current. Any trigger can drive it: a webhook, a schedule, or an agent responding to something that happened elsewhere in your stack.

Deliverability reporting that lands in a database

Brevo: Get Email Daily Reports returns one row per day with requests, delivered, bounces, opens, clicks, spam reports, and unsubscribes, and the node states its window contract plainly, including the one that bites: limit defaults to 10 day rows, so a 30-day window comes back looking complete at 10 days unless you raise it. Brevo: Get Email Aggregated Report gives whole-window totals, and Brevo: Get Email Events is the per-message log. A scheduled sweep can write all of it into a Mattering database and open a task when bounces spike.

SMS with credit awareness built in

Brevo: Send Transactional SMS delivers one message and reports remainingCredits, smsCount, and usedCredits on its output, so a workflow can watch the balance it is spending. SMS campaigns get the same draft-then-send treatment as email, with Brevo: Send Test SMS Campaign for a real test message first. SMS sending draws on prepaid message credits purchased separately in Brevo on every plan, so credit awareness is not optional.

Brevo events driving Mattering workflows

Brevo: Create Webhook points Brevo at any URL, including a Mattering inbound webhook trigger, so deliveries, opens, clicks, bounces, and contact changes can start workflows the moment they happen: a hard bounce can flag the contact in your database, an unsubscribe can update the CRM record. Webhooks come in transactional, marketing, and inbound types, and the list, update, and delete nodes manage them from the same canvas.

Example: A signup lands: create the contact, file it on a list, send the welcome email

Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.

1

Trigger: an inbound webhook fires when a signup form is submitted, carrying the email address and name.

2

Brevo: Create Contact creates the contact with updateEnabled true, so a repeat signup updates the existing record instead of failing the run.

3

Brevo: Add Contacts To List files the contact on the newsletter list that the next campaign will target.

4

Brevo: Send Transactional Email sends the welcome email from an active template, with the contact's name substituted through params, and returns a messageId.

5

The workflow writes the signup into a Mattering database next to the rest of the funnel, messageId included.

6

A condition checks the send output and opens a task in Mattering Productivity when the send failed, so a broken welcome email surfaces as work instead of silence.

Brevo MCP questions, answered

What Brevo operations are supported?

50 nodes on the Brevo v3 REST API: 21 query nodes and 29 action nodes covering the account probe, contacts (list, get, create, update, delete, and bulk import with process polling), lists and folders with membership management, contact attributes, email campaigns (list, get, create, update, delete, send now, send test), transactional email (send, template management, the event log, and per-day and aggregated statistics), SMS campaigns with the same lifecycle, transactional SMS, verified senders, and webhooks. Deliberately not included: Brevo's CRM deals and companies, Conversations, WhatsApp, ecommerce and coupons, inbound parsing, and sub-account management, which are separate product surfaces.

Does this work with Claude, ChatGPT, or other AI assistants?

Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively.

Brevo has an official MCP server. Why use this connector?

Brevo documents an official MCP server at mcp.brevo.com, with MCP tokens generated alongside API keys in the dashboard, and if all you want is an assistant talking to Brevo alone, it is a genuine option. This connector earns its place when Brevo is one step in a larger workflow: the same canvas holds your other connectors and the Mattering platform itself, so a signup can create a contact and then open a follow-up task, a campaign send can wait behind a human approval step, and statistics can land in a database next to the rest of your work. Credentials live with your other connector secrets, and the same nodes serve visual automations and AI agents alike.

Do I need a paid Brevo plan?

No. Brevo's Free plan includes 300 email sends per day, resetting daily, with storage for up to 100,000 contacts, and its feature list includes email and SMS campaigns and transactional email and SMS. The connector's whole read surface, contacts, lists, campaigns, templates, statistics, senders, and webhooks, works on a free account. SMS sending is the exception on every plan: it draws on prepaid message credits purchased separately in Brevo.

What are Brevo's API rate limits?

Brevo publishes per-family limits, and they vary enormously. On the general tier, transactional email sending allows 1,000 requests per second, contacts endpoints allow 10 per second, transactional SMS allows 150 per second, and other transactional email endpoints allow 300 per hour. The one to plan around is the catch-all: campaigns, lists management, webhooks, account, and everything else share 100 requests per hour. Exceeding a limit returns HTTP 429, which nodes report on their output rather than silently retrying. Professional and Enterprise plans roughly double these, and Enterprise can request extended limits. Keep polling loops against campaign and process endpoints gentle.

Can an automation send email or SMS safely?

Yes, and the guardrails are explicit rather than implied. All six send nodes are flagged destructive, because a delivered email or SMS cannot be recalled, and that includes the test send nodes: Send Test Email Campaign and Send Test SMS Campaign put real messages in real inboxes and phones. Campaign creation is draft-first, so Create Email Campaign and Create SMS Campaign deliver nothing on their own. The honest pattern is assemble the draft, test send to your own team, gate the real send behind a condition or an approval task, and only then let Send Email Campaign Now or Send SMS Campaign Now fire.

Why is Import Contacts flagged destructive when it deletes nothing?

Because of what it overwrites. Brevo's import defaults updateExistingContacts to true, so a bulk import silently rewrites the attribute values of every existing contact it matches, at file scale, with no undo, and emptyContactsAttributes true goes further by erasing attributes the import leaves blank. A miskeyed CSV can flatten thousands of records in one call. The import runs in the background and returns a processId, which Brevo: Get Process polls to completion with invalid and duplicate counts, but completion is not reversal, so the destructive flag makes workflows gate it.

How do the email statistics nodes work?

Three nodes, three shapes. Brevo: Get Email Daily Reports returns one row per day for a startDate and endDate window, and the node declares its window contract, including the detail that trips people: limit defaults to 10 day rows, so a 30-day window silently comes back as 10 days unless you raise it, and the days parameter is an alternative to the window pair, not a companion. Brevo: Get Email Aggregated Report returns one total for the whole window, and it is the right source for unique opens and unique clicks, because the daily rows count uniques within each day and summing them across days overcounts. Brevo: Get Email Events is the per-message log with timestamps, for tracing rather than reporting.

50 nodes waiting on the canvas

Put Brevo to work inside your workspace

Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.

All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Brevo is a product of its respective owner; Mattering is an independent platform.

Start Free Explore our Products