Menu

Mattering Automations Brevo integration

Connect Brevo to Mattering Automations: contacts, lists, and folders, email and SMS campaigns from draft to send, transactional email with templates and delivery statistics, transactional SMS, senders, and webhooks as workflow steps, authenticated with one API key.

The Mattering Automations Brevo integration adds the Brevo v3 REST API to your automation canvas: manage contacts with their attributes, lists, and folders, run bulk imports with background process polling, take email campaigns from draft through test send to delivery, do the same for SMS campaigns, send transactional email from templates and transactional SMS, read per-day and aggregated delivery statistics and the transactional event log, list verified senders, and manage the webhooks that push Brevo events back into your workflows.

The credential is a single API key created in the Brevo dashboard under SMTP & API, then API Keys, and sent as the api-key header on every request. One key grants the account's entire v3 REST surface, because Brevo has no per-key scoping, so the key is a master credential and belongs nowhere except the connector. Brevo's SMTP relay uses a separate SMTP key type that this integration never needs. Setup takes a few minutes, and this guide walks through each step and ends with the full node reference.

The safety modeling is stated on the nodes rather than buried. Of the 50 nodes, 21 read and 29 act, and 13 carry a destructive flag: the six senders, Brevo: Send Transactional Email, Brevo: Send Transactional SMS, Brevo: Send Email Campaign Now, Brevo: Send SMS Campaign Now, Brevo: Send Test Email Campaign, and Brevo: Send Test SMS Campaign, because a delivered message cannot be recalled and even test sends reach real inboxes and phones, the six deletes, Brevo: Delete Contact, Brevo: Delete List, Brevo: Delete Email Campaign, Brevo: Delete Email Template, Brevo: Delete SMS Campaign, and Brevo: Delete Webhook, and Brevo: Import Contacts, because Brevo's default updateExistingContacts true overwrites existing contacts' attributes in bulk with no undo. Brevo's CRM deals, Conversations, WhatsApp, ecommerce, and sub-account surfaces are separate products and are deliberately not part of this integration.

Before you start

  • A Brevo account. The Free plan is enough to build with: it includes 300 email sends per day, resetting daily, storage for up to 100,000 contacts, and email and SMS campaign and transactional features, and the integration's entire read surface, contacts, lists, campaigns, templates, statistics, senders, and webhooks, works on it.
  • For SMS sending, prepaid message credits purchased in Brevo. SMS draws on prepaid credits on every plan, and Brevo: Send Transactional SMS reports the remaining balance on its output.
  • At least one verified sender in Brevo, because campaign creation and transactional email sends need a verified sender email. Brevo: List Senders fetches them once connected.
  • A Mattering workspace with access to the Automations app.
  • A note on request budget before you design polling loops: on Brevo's general tier, campaigns, lists management, webhooks, and account endpoints share a catch-all limit of 100 requests per hour, far below the contacts endpoints at 10 requests per second. Schedule sweeps accordingly.

Create a Brevo API key

Mattering authenticates to Brevo with a single API key sent as the api-key header on every request. Brevo has no per-key scoping: any valid key can read and write the whole v3 REST surface, from contacts to campaign sends. That cuts both ways. There are no permission groups to get wrong, so a key that connects will run every node, and it means the key deserves master-credential handling: name it for this integration, store it only in the Mattering credential, and rotate it from the same dashboard page if it ever leaks.

Sign in at app.brevo.com, open your account menu in the top right, and choose SMTP & API.
Open the API Keys tab. This page lists the account's REST API keys; the SMTP tab next to it manages relay keys, which are a different credential this integration does not use.
Click Generate a new API key, name it for its job, for example Mattering Automations, and generate it.
Copy the key and store it nowhere except the Mattering credential. A Brevo API key is unscoped: it grants the account's entire REST API, including contact deletion and live email and SMS sends. If it is ever exposed, delete it on this page and generate a replacement.
If your Brevo account also uses the SMTP relay, do not confuse the two key types: the REST API key from the API Keys tab is the one this integration accepts. An SMTP key pasted into the credential fails the connection test with a 401.

Connect Brevo to Mattering

In Mattering Automations, open Connectors and click Add Connector.
Choose Brevo from the list.
Click Create new credential, paste the API key, and save.
The credential is stored encrypted in Google Secret Manager and never appears in workflow logs.
Click Test Connection. Mattering calls Brevo's account endpoint, which works for every valid key: a successful result proves the credential, and a 401 with Key not found means the key is mistyped, deleted, or the wrong key type.
Click Connect. All 50 Brevo nodes appear in your canvas palette.

How webhook triggers deliver

Brevo pushes events to Mattering the moment they happen; no polling, no schedules.

Event happens

An event you subscribe to in Brevo

Delivery to your webhook URL

Mattering reads the event type and matches it to your trigger nodes

Your workflows run

Every active automation containing the trigger node fires

Verify it works

After connecting, open any automation canvas and check the palette: a Brevo section should list the query and action nodes. Drop Brevo: Get Account onto the canvas and run a test step. It is the integration's universal probe: it takes no parameters, works for every valid key, and returns the account's plan and remaining email and SMS credits without echoing the secret. If this node succeeds, the credential is healthy; anything failing after it is a parameters question, not an authentication one, because Brevo keys have no permission scoping to be missing.

Next, run the id fetchers your workflows will lean on: Brevo: List Lists for list ids, which feed every list-scoped node and campaign recipient field, Brevo: List Senders for the verified sender emails that campaign and transactional sends require, and Brevo: List Attributes for the CAPITAL-named attributes that contact create and update calls reference. Everything in this verify path is read-only: it cannot reach the 13 destructive nodes or deliver a single message. One budget note: these management endpoints sit in Brevo's 100 requests per hour catch-all bucket on the general tier, so verify by hand rather than in a tight loop.

Node reference

50 nodes, generated from the connector itself so this reference always matches what ships.

Read and query nodes 21

Brevo: Get Account

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

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

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

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

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

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

brevo_get_folder_lists

List the contact lists inside one folder.

Brevo: Get List

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

brevo_get_list_contacts

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

Brevo: Get Process

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

brevo_get_sms_campaign

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

Brevo: List Attributes

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

brevo_create_folder

Create a folder for organizing contact lists.

Brevo: Create List

brevo_create_list

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

Brevo: Create SMS Campaign

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

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

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

brevo_delete_email_campaign

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

Brevo: Delete Email Template

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

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

brevo_delete_sms_campaign

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

Brevo: Delete Webhook

brevo_delete_webhook

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

Brevo: Import Contacts

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

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

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

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

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

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

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

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

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

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

brevo_update_email_template

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

Brevo: Update List

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

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

brevo_update_webhook

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

Using the integration

On the automation canvas

Brevo nodes chain with every other node: a signup webhook can run Brevo: Create Contact and Brevo: Add Contacts To List and then open a follow-up task in Mattering Productivity, a nightly sweep can write Brevo: Get Email Daily Reports rows into a Mattering database, and Brevo: List Contacts can feed an audience audit that lives next to the rest of the work. The list id from Brevo: List Lists and the sender email from Brevo: List Senders are the two values most downstream nodes ask for, and the connector's field pickers offer them inline.

From AI assistants over MCP

Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and Matter can drive the same surface. An agent can look up a contact with Brevo: Get Contact, file it on a list, draft a campaign with Brevo: Create Email Campaign, and read the results back through the statistics nodes. The read nodes are the safest surface to hand an agent; keep the 13 destructive nodes, especially the six senders, behind conditions or approval steps, because a sent message is the one thing no workflow can take back.

Campaigns are drafts until a send node fires

Brevo: Create Email Campaign and Brevo: Create SMS Campaign produce drafts, and drafts deliver nothing, which is what makes campaign assembly safe to automate. Content for an email campaign is exactly one of htmlContent, htmlUrl, or templateId, and recipients nest list ids with optional exclusion lists. Brevo: Send Test Email Campaign puts real test emails in your team's inboxes, up to 50 test emails per day, and Brevo: Send Test SMS Campaign sends a real message to a phone number that must belong to a non-blacklisted contact on the account. The real sends, Brevo: Send Email Campaign Now and Brevo: Send SMS Campaign Now, deliver to the entire recipient list immediately and cannot be recalled, so gate them behind an approval task.

Transactional email and the statistics windows

Brevo: Send Transactional Email sends from inline content or an active template via templateId with params substitution and returns a messageId. For reporting, Brevo: Get Email Daily Reports returns one row per day for a startDate and endDate window, and its window contract is declared on the node, including the detail that quietly truncates: limit defaults to 10 day rows, so a 30-day window comes back as 10 days unless you raise it, and the days parameter is an alternative to the window pair, rejected when combined with it. Brevo: Get Email Aggregated Report returns whole-window totals and 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 for tracing individual recipients.

Imports run in the background

Brevo: Import Contacts accepts JSON rows, CSV text, or a hosted file URL up to 10MB, targets existing lists or a new list, and returns HTTP 202 with a processId rather than a result: the import happens in the background. Poll Brevo: Get Process until the status is completed; the finished process reports invalid and duplicate counts. The node is flagged destructive because Brevo defaults updateExistingContacts to true, so matched contacts get their attribute values overwritten at file scale with no undo, and emptyContactsAttributes true erases attributes the import leaves blank. Review the file before the run, not after.

Webhooks deliver Brevo events to your workflows

Brevo: Create Webhook points Brevo at any URL, including a Mattering inbound webhook trigger, so deliveries, opens, clicks, bounces, unsubscribes, and contact changes can start workflows the moment they happen. Webhooks come in transactional, marketing, and inbound types, and the transactional and marketing types require an events list at creation. Brevo: List Webhooks returns each webhook's complete configuration, Brevo: Update Webhook changes the URL or event subscriptions in place, and the destructive-flagged Brevo: Delete Webhook stops delivery immediately without replaying missed history.

Troubleshooting

Test Connection fails with a 401 Key not found error
Brevo returns 401 with Key not found for any credential it does not recognize. Check for leading or trailing whitespace from the copy, confirm the key still exists on the API Keys tab at app.brevo.com under SMTP & API (a deleted key fails exactly like a wrong one), and confirm it is a REST API key rather than an SMTP key: the SMTP tab's relay keys are a different credential type and are always rejected here. There are no permission scopes to diagnose; if the key is valid, it connects.
Campaign, list, or webhook nodes return 429 while contact nodes run fine
That split is Brevo's published rate model, not a fault. Contacts endpoints allow 10 requests per second on the general tier, but campaigns, lists management, webhooks, account, and most other endpoints share a catch-all bucket of 100 requests per hour. A workflow that polls a campaign or lists endpoint in a loop drains that bucket quickly, and further calls return HTTP 429, which nodes report on their output rather than silently retrying. Spread scheduled sweeps apart, fetch lists once per run instead of per item, and where volume is real, note that Professional and Enterprise plans roughly double the limits.
Get, Update, or Delete Contact reports the contact does not exist when it clearly does
Brevo addresses contacts by more than email: the identifier can be an email address, the numeric contact id, an SMS number, or an ext_id, and the optional identifierType parameter tells Brevo which kind you passed (email_id, contact_id, phone_id, ext_id, and related values). A phone number or ext_id passed without its identifierType is looked up as the wrong kind and comes back not found. Pass the discriminator whenever the identifier is not a plain email address, and remember emails are unique per account, so email is the calmest identifier for automations.
Get Email Daily Reports returns fewer days than the window asked for
The limit parameter caps the number of day rows returned and defaults to 10, so a 30-day startDate and endDate window silently comes back as 10 rows that look complete. Raise limit to at least the number of days in the window, and compare the row count you receive against it. Two more window rules from Brevo's reference: days is an alternative to the startDate and endDate pair and is rejected when combined with them, and the days form caps at 30.
Import Contacts succeeds instantly but the contacts are not in Brevo
The import endpoint returns HTTP 202 with a processId, meaning accepted, not finished: the actual import runs as a background process. Chain Brevo: Get Process on the processId and poll until status is completed; the finished process carries invalid and duplicate counts that tell you what the file actually did. If rows are missing after completion, those counts are the first place to look, along with the 10MB body cap and the requirement to target existing listIds or request a new list.
Create Email Campaign is rejected with a validation error
Three requirements cover most rejections. Content must be exactly one of htmlContent, htmlUrl, or templateId: zero or two of them fails. The sender must be provided and must correspond to a verified sender on the account; fetch valid ones with Brevo: List Senders. And recipients are nested: list ids go in the recipients object's listIds array, not at the top level, with exclusionListIds alongside. The node's field layout maps these for you, but values templated in from earlier steps still have to satisfy them.
Send Test SMS Campaign fails while the campaign itself looks healthy
Brevo requires the test phone number to belong to an existing contact on the account that is not blacklisted for SMS. An arbitrary phone number, even a real one, is rejected. Create the contact first with the SMS number in its attributes, confirm it is not blacklisted, and retest. Test SMS messages are real deliveries that consume a prepaid credit, which is also why the node carries a destructive flag.
Update and delete nodes return an empty result
That is Brevo's success shape, not a failure. Brevo's update, delete, and several create endpoints return an empty body on success (HTTP 200 or 204), so the node's output data is an empty object and there is nothing further to parse. Treat the step succeeding as the confirmation, and when a workflow needs the resulting state, follow with the matching read node, for example Brevo: Get Contact after an update. Errors, by contrast, always carry a code and message pair on the output.
Add Contacts To List fails on a large batch
The emails array caps at 150 addresses per request, and the node sends exactly one of emails, ids, or extIds: mixing forms in one call fails. For additions beyond the cap, loop in batches of 150 or switch to Brevo: Import Contacts targeting the list, which handles bulk properly through a background process. Mind the request budget while looping: list management calls draw from the 100 requests per hour catch-all bucket on the general tier.

Brevo is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.

Start Free Explore our Products