Building a Brevo integration: email, SMS and WhatsApp from one European platform
Brevo (formerly Sendinblue) is a French communications platform that brings together transactional email, marketing automation, SMS, WhatsApp Business and live chat in a single API layer. For European B2B businesses that want to work GDPR-first, it is an attractive combination: all data stays within the EU, the platform falls under French and EU law, and the standard data processing agreement is GDPR-compliant. We integrate Brevo with your web application, e-commerce back end, CRM or customer portal, so that triggers in your system result directly in a confirmation email, a 2FA text message or a WhatsApp message.
Discuss your Brevo integration View use casesWhat Brevo is and why European businesses choose it
Brevo positions itself as an all-in-one customer communication platform. The same API and dashboard handle transactional messages, marketing campaigns, marketing automation, SMS, WhatsApp Business and a live chat widget. For European B2B businesses, the combination of EU data residency, GDPR-first design and a single supplier often outweighs what American competitors offer.
The platform was founded in Paris in 2012 as Sendinblue and renamed Brevo in 2023. Its legal seat is in France, its own infrastructure runs on European data centres, and its standard privacy and DPA documentation is written from an EU perspective rather than a retrofitted American policy. That removes legal friction around data processing agreements, DPIAs and questions from your own customers about where their data is stored.
For your developers, the appeal is practical: a single REST API and one SMTP relay deliver email, SMS and WhatsApp. You manage contact lists, segments and automation flows from one dashboard, while your application sends transactional messages through a few API calls. That is a different model from a patchwork of point solutions, where you combine Mailgun or SendGrid for transactional email, Mailchimp for marketing and Twilio for SMS, with three contracts, three SDKs and three processing agreements.
We build Brevo integrations that turn these benefits into concrete integrations: from your checkout, your onboarding flow, your customer portal or your operational system. Not a standalone "email marketing" package alongside your application, but communication built into the work processes that keep your business running.
Use cases for which we integrate Brevo
Whether you run a SaaS product, manage an online shop or are a B2B service provider with a customer portal, the same Brevo account covers both critical transactional messages and marketing communication. The use cases below come up often in our projects.
Transactional email
Order confirmations, invoice emails, password resets, account activation, magic links and notifications. We connect your application to Brevo via the transactional API or the SMTP relay, configure SPF, DKIM and DMARC on your own domain, and set up list-unsubscribe headers where relevant. This ensures every message arrives and your sender reputation stays high.
SMS and 2FA
Order confirmations, appointment reminders, delivery notifications and 2FA codes by SMS. The Brevo SMS API uses the same authentication as the email API and delivers internationally, including to European countries where American providers have patchy coverage. For 2FA flows we build idempotent endpoints with retry logic.
WhatsApp Business
Brevo Conversations and the Marketing Conversations API give you access to WhatsApp Business with approved message templates for reminders, status updates and marketing messages. We handle the template application with Meta, connect webhooks for incoming messages, and route conversations through to your helpdesk or CRM.
Marketing automation
Drip campaigns with conditional flows: a welcome series for new users, a re-engagement flow for inactive customers, an upgrade flow for trial users who perform certain actions. Brevo's automation builder works with events from your application; we send those events via the API so the flows respond to real user behaviour, not just time-based triggers.
Lightweight CRM for SMEs
Brevo includes a lightweight CRM module for SMEs that do not want to set up Salesforce or HubSpot. Deals, tasks, pipelines, notes and interaction history, all linked to the same contacts you send mailings to. We synchronise this data two-way with your existing system, or use Brevo CRM as the sole source for lead management.
Live chat and chat widget
The Brevo chat widget on your website connects to the same contacts and conversation database. A visitor who asks a question in chat can later be addressed under the same identity in a marketing email or WhatsApp flow. We integrate the chat with your helpdesk routing and make sure everything runs on your own domain, without external scripts that disrupt your cookie banner.
How Appfront builds a Brevo integration
We build Brevo integrations that fit your existing architecture, not the other way round. Sometimes that means a thin service layer in your existing backend that calls the Brevo API; sometimes a separate microservice that handles all communication and consumes events from a queue. The choice depends on volume, criticality and what you already have running.
For every integration, we first take stock of the message types: which triggers are transactional and must be delivered within seconds, which messages are marketing and can go through the bulk pipeline, and which channels you want to use in parallel (email only, or also SMS and WhatsApp). Based on that, we choose between the Transactional API, the Marketing Campaigns API and the Conversations API. They sit alongside each other but have different rate limits and endpoints.
For sender configuration, we set up your own domain with SPF, DKIM, DMARC and, where relevant, BIMI with a verified VMC certificate. We add list-unsubscribe headers to marketing emails to comply with the Gmail and Yahoo guidelines for bulk mail. We connect Brevo webhooks (bounces, opens, clicks, unsubscribes, spam complaints) to an endpoint in your application or to a logging pipeline so you can automate follow-up.
From first API call to live production
Our approach to a Brevo integration follows four phases. Each phase delivers a concrete, testable result, with no months of planning without working code.
Discovery and domain setup
We map your triggers and channels, choose the right API endpoints and set up your sending domain with SPF, DKIM and DMARC. We decide on sub-account and IP choices (shared or dedicated) based on expected volume.
Back-end integration
We build a service layer that translates your application events into Brevo API calls: transactional, SMS, WhatsApp, contact updates. Idempotency, retries and exponential backoff are built in as standard.
Automation and segmentation
We set up the marketing flows and segmentation rules in Brevo, fed by custom attributes and events from your application. We design templates in Brevo's editor or deliver them as responsive HTML.
Monitoring and optimisation
We connect webhooks for bounces, complaints and unsubscribes to logging and alerting. We monitor reputation, deliverability and open rates on an ongoing basis, so timely adjustments remain possible.
Brevo compared with SendGrid, Mailchimp and Klaviyo
Brevo operates in the same market as SendGrid (transactional), Mailchimp (marketing) and Klaviyo (e-commerce CRM), but makes different choices. For a European B2B company with GDPR requirements, the balance often tips towards Brevo.
Brevo versus SendGrid
SendGrid is the American market standard for transactional email, owned by Twilio and hosted on American infrastructure. For European companies that want to keep data within the EU and avoid the Standard Contractual Clauses discussion, Brevo is the more logical choice. Functionally, the transactional features are comparable; legally, and in EU deliverability for EU traffic, Brevo often has the edge.
Brevo versus Mailchimp
Mailchimp is strong in audience management and consumer marketing, but its pricing is aggressively based on the number of contacts, and it is hosted in the US. Brevo bills by default on the number of emails sent per day or month rather than on contacts, which works out cheaper for B2B companies with larger lists and lower sending frequency. EU data residency comes on top of that.
Brevo versus Klaviyo
Klaviyo specialises in e-commerce: deep Shopify and Magento integrations, predictive analytics on purchasing behaviour, and powerful flows. For a purely e-commerce B2C business with high volumes, Klaviyo is often the better choice. For B2B companies with SaaS, services or mixed-use cases, Brevo is more broadly applicable, mainly because SMS and WhatsApp are included on the same platform.
Brevo versus Mailgun and Postmark
Mailgun and Postmark are pure transactional providers with strong deliverability and developer tooling. Brevo covers both transactional and marketing in one platform, which is administratively lighter. For high transactional volumes with strict deliverability requirements, a dedicated transactional provider may still be a better fit. We will give you an honest view of which way your situation weighs more heavily.
Brevo's API stack and how we use it
Brevo offers a REST API with separate endpoints for transactional, marketing, SMS, WhatsApp, contacts, lists, campaigns, automation and CRM. There is also an SMTP relay for applications that prefer to work via standard mail protocols. The API documentation is publicly available at developers.brevo.com and includes official SDKs for Node.js, PHP, Python, Ruby, Java and C#.
When building an integration, we choose the right path for each use case. For transactional email from a Laravel or Symfony application, we often work with the Symfony Mailer driver or a thin PHP SDK layer. For a Node.js microservice we use the official @getbrevo/brevo SDK. For legacy applications still running on SMTP, the SMTP relay is a quick migration strategy that requires no major code changes. We process Brevo webhooks in a separate queue consumer, so a slow webhook response never blocks your application.
Authentication runs via an API key in the api-keyheader. For multi-tenant SaaS platforms we use sub-accounts: each customer gets an isolated Brevo environment with its own sender domain and its own statistics. For rate limiting we follow Brevo's documentation and build a retry layer with exponential backoff for 429 responses. For compliance-relevant triggers (password resets, invoice confirmations) we log every API call with a correlation ID, so audits remain traceable later.
GDPR, EU data residency and compliance
For European B2B companies, communication infrastructure is often a stumbling block in privacy assessments. Brevo takes a number of decisions in this area that shorten the DPIA and the record of processing activities.
EU data residency by default
Contact details, email content, statistics and logs are stored on infrastructure within the European Union. There is no optional EU region that you have to tick yourself, as with some American providers; it is the default setting, which considerably simplifies legal arguments and transfer assessments.
GDPR-compliant DPA
Brevo's standard data processing agreement is drawn up under French and EU law and contains the usual GDPR clauses: purpose limitation, sub-processors, security measures, breach notification and data subject rights. For most B2B projects, no additional DPA is required.
ISO 27001 certification
Brevo's infrastructure and operational processes are ISO 27001 certified. For clients in regulated sectors (financial services, healthcare, government), this provides a verifiable starting point for supplier due diligence and information security audits.
French and EU law
The legal seat is in Paris and the applicable law is French and European. In the event of disputes or requests from authorities, this is handled through European legal frameworks, not through US subpoena procedures or the CLOUD Act.
Real-world scenarios from our practice
The examples below illustrate what a Brevo integration looks like in practice for different types of business. The technical building blocks are similar; the implementation differs from case to case.
SaaS platform with onboarding flow
A B2B SaaS product registers new accounts via its own sign-up. On sign-up, the application sends a verification email via the transactional API; after verification, a five-step onboarding drip starts using Brevo's automation. Triggers within the app (first import, first report, first team member invited) send events back to Brevo so the drip skips what the user has already done. Inactive trial users receive a re-engagement email after seven days; converters are removed from the drip flow.
Webshop with SMS delivery updates
An e-commerce platform sends order confirmations by email and delivery updates by SMS. The order service publishes events to a queue; a communications microservice consumes these and calls the appropriate Brevo endpoints. At high volumes, this runs on a dedicated IP pool, with DKIM on the webshop domain and monitoring of bounce rates. WhatsApp status updates are an opt-in choice during checkout, delivered through the same Brevo account.
Client portal with 2FA and invoicing
A service provider with a client portal sends 2FA codes by SMS, invoice emails with PDF attachments via the transactional API, and quarterly newsletters via Marketing Campaigns. One Brevo account, three endpoints, three audit streams. For the 2FA flow, we use idempotency keys, and if Brevo does not respond within the SLA, the service falls back to a backup provider within 30 seconds.
B2B lead generation with conversational marketing
A small or medium-sized business without its own CRM uses Brevo CRM for lead management and the chat widget for inbound leads. A visitor who asks questions in chat automatically enters the CRM pipeline; follow-up emails go through the same account. WhatsApp Business closes the loop for international leads. Sales staff work in a single Brevo dashboard; export to accounting software runs via the Contacts API.
Why Appfront for your Brevo integration
Integration and deliverability expertise
We have integrated email and messaging platforms with Laravel, Symfony, Node.js and Django applications. Domain setup, SPF, DKIM, DMARC, BIMI and list-unsubscribe headers are standard parts of our delivery checklist, not something you have to work out yourself later.
EU-first design
We design integrations with EU data residency, GDPR compliance and transparent processing as the starting point. For clients in regulated sectors, we work with DPIA input, audit logging and correlation IDs so that accountability is always traceable after the fact.
One partner for stack and strategy
Brevo is one building block in a larger communication architecture. We help you think through how it fits into your existing stack, which messages go through which channels, and how automation and segmentation align with your product data. Not a loose integration, but a considered communication layer.
Frequently asked questions about Brevo integrations
Ready to build a Brevo integration?
Discuss your situation with us. We'll map out the message types, channels and compliance requirements, and deliver a concrete proposal, free of charge and without any obligation.
Schedule a conversation