Marketing Automation · Integration
Brevo
Add Brevo to your product for your customers, and give your AI agents governed access to it.
Brevo, which was Sendinblue until 2023, carries two things most email platforms keep apart: a marketing side with contacts, lists, folders and campaigns, and a transactional side that sends one message against a template with parameters filled in. Both run on the same contact record, which is convenient and also the source of the mistake people make, because a transactional send does not respect a marketing unsubscribe and must not be used to route around one. Contact attributes are typed and defined per account, so an integration reads the attribute definitions rather than assuming a field exists. Outcomes arrive as webhook events, delivered, opened, clicked, hard bounced, soft bounced, marked spam and unsubscribed, which is what your product should act on rather than a report the next morning. Each customer brings their own API key, so sends come out of their plan and their sending reputation.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Brevo account so mail sends from their domain and counts against their own plan.
Read the account's contact attribute definitions before writing, so a custom field only that customer has is mapped rather than dropped.
Send a transactional email or SMS against a template with parameters, kept deliberately separate from marketing consent.
Take delivery, open, click, bounce and unsubscribe events by webhook, so a hard bounce is handled rather than discovered in a report.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports how a campaign performed from its own open, click and bounce counts.
An agent adds a contact to a list or updates an attribute within scoped permissions, with the change logged.
An agent explains why a message never arrived by reading the event trail for that address.
Example prompt
Why did this contact not receive the onboarding email, and are they sitting on a suppression list?
Set up Brevo in 4 steps
- 01Enable the Brevo connector in your fastn dashboard.
- 02Have each customer create their own API key, so sends come off their plan and their sending reputation rather than yours.
- 03Read that account's attribute definitions and map them, then subscribe to the delivery events your product acts on.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Brevo integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Brevo integration without building it. Your customers connect their own Brevo account inside your product and work their campaigns, segments and subscribers there, with no per-customer code on your side.
- Handle the part that actually costs time: engagement data arrives as a high-volume event stream, so ordering and deduplication matter. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Brevo update is not your on-call problem.
- One integration serves your product and your agents. The same governed Brevo connection powers in-product features and gives AI agents scoped, audited access, so you trigger and measure campaigns from inside your product without wiring it twice.
Used by these teams
Compare with
Mailchimp
MailerLite
ActiveCampaignOften used alongside
Tools the same teams tend to run next to Brevo, across other categories.
Salesforce
HubSpot
Pipedrive
Zoho CRMBrevo integration FAQ
How do I add a Brevo integration to my product?
Enable the Brevo connector in your fastn dashboard, then let each customer authenticate their own Brevo account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Brevo client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Brevo account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Brevo account and only ever sees their own campaigns, segments and subscribers. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Brevo integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reports how a campaign performed from its own open, click and bounce counts.
Who maintains the Brevo integration?
fastn does. When Brevo changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can I trigger a Brevo campaign from an event in my product?
Yes. Product events can start a campaign, add a contact to a segment, or enrol someone in a journey, so lifecycle messaging follows what a user actually did rather than a nightly export.
Can I read engagement results back from Brevo?
Yes. Results come back scoped per tenant, so your product can act on them without one customer's data mixing with another's. What you get depends on the channel: opens, clicks, bounces and unsubscribes where there are sends, and impressions, spend and conversions where there are campaigns.
What can I build with the Brevo integration?
A common starting point: let each customer connect their own Brevo account so mail sends from their domain and counts against their own plan. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Brevo integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Brevo does not change your per-connector cost. You can start free with 3 connected accounts.
Add Brevo to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.