Building a Brevo integration: email, SMS and WhatsApp from one European platform
Brevo (formerly Sendinblue) is a French communication platform that brings transactional email, marketing automation, SMS, WhatsApp Business and live chat together in a single API layer. For European B2B companies that want to work GDPR-first, that is an attractive combination: all data stays within the EU, the platform is subject to French and EU law, and the standard data processing agreement is GDPR-compliant. We integrate Brevo with your web application, e-commerce backend, CRM or customer portal, so that triggers in your system immediately result in a confirmation email, a 2FA SMS or a WhatsApp message.
Discuss your Brevo integration View use casesWhat Brevo is and why European companies choose it
Brevo positions itself as an all-in-one customer communication platform. The same API and the same dashboard handle transactional messages, marketing campaigns, marketing automation, SMS, WhatsApp Business and a live chat widget. For European B2B companies, the combination of EU data residency, a GDPR-first approach and a single supplier is often decisive compared with American competitors.
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 the standard privacy and DPA documentation was drawn up from an EU perspective, not as an American policy translated after the fact. That reduces legal friction with 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 a single SMTP relay deliver email, SMS and WhatsApp. You manage contact lists, segments and automation flows through one dashboard, while your application sends transactional messages with a few API calls. That is a different model from a stack of point solutions in which you combine Mailgun or SendGrid for transactional email with Mailchimp for marketing and Twilio for SMS: three contracts, three SDKs, three data 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, operate a webshop 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. That way 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 European countries where US 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 request with Meta, connect webhooks for incoming messages and route conversations on 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 don't 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 sync this data two-way with your existing system, or use Brevo CRM as the single source for lead management.
Live chat and chat widget
The Brevo chat widget on your website draws on the same contact 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 mess up your cookie banner.
How Appfront builds a Brevo integration
We build Brevo integrations that fit your existing architecture, not the other way around. 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 map out 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 SMS and WhatsApp too). Based on that, we choose between the transactional API, the Marketing Campaigns API and the Conversations API. They coexist but have different rate limits and endpoints.
For sender configuration, we set up your own domain: 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 email. 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 running in 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 sender domain with SPF, DKIM and DMARC. We decide on sub-account and IP options (shared or dedicated) based on expected volume.
Backend 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 you can adjust in good time.
Brevo compared with SendGrid, Mailchimp and Klaviyo
Brevo competes 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 shifts 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 their data within the EU and avoid the Standard Contractual Clauses debate, Brevo is the more logical choice. Functionally, the transactional features are comparable; legally, and in EU deliverability, Brevo often has the edge for EU traffic.
Brevo versus Mailchimp
Mailchimp is strong in audience management and consumer marketing, but its pricing scales aggressively with 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, not on contacts, which is cheaper for B2B companies with larger lists and a lower sending frequency. EU data residency is a further advantage.
Brevo versus Klaviyo
Klaviyo specialises in e-commerce: deep Shopify and Magento integrations, predictive analytics on purchasing behaviour and powerful flows. For a pure B2C e-commerce company with high volumes, Klaviyo is often the better choice. For B2B companies with SaaS, services or mixed use cases, Brevo is more broadly applicable, not least because SMS and WhatsApp come from the same platform.
Brevo versus Mailgun and Postmark
Mailgun and Postmark are pure transactional providers with strong deliverability and developer tooling. Brevo covers transactional and marketing in one, which is lighter on administration. With high transactional volumes and strict deliverability requirements, a dedicated transactional provider may still be a better fit; we give you honest advice on which side carries more weight in your situation.
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 approach 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 without major code changes. We process Brevo webhooks in a separate queue consumer so that 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 on 429 responses. For compliance-relevant triggers (password resets, invoice confirmations), we log every API call with a correlation ID so that audits can be traced later.
GDPR, EU data residency and compliance
For European B2B companies, communication infrastructure is often a stumbling block in privacy assessments. Brevo makes a number of choices in this area that shorten your DPIA and record of processing activities.
EU data residency by default
Contact data, email content, statistics and logs are stored on infrastructure within the European Union. It is not an optional EU region you have to tick yourself, as with some US providers, but the default setting, which considerably simplifies legal argumentation 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, data breach notifications and data subject rights. For most B2B projects, no additional DPA is needed.
ISO 27001 certification
Brevo's infrastructure and operational processes are ISO 27001 certified. For customers in regulated sectors (financial services, healthcare, government), that provides a verifiable starting point for supplier due diligence and information security audits.
French and EU law
The registered office is in Paris and the governing law is French and European law. In the event of disputes or enquiries by authorities, this runs through European legal frameworks, not through US subpoena procedures or the CLOUD Act.
Concrete 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 per situation.
SaaS platform with an onboarding flow
A B2B SaaS product registers new accounts through its own signup. At signup, the application sends a verification email via the transactional API; after verification, a five-step onboarding drip starts via Brevo's automation. Triggers in 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 communication microservice consumes them and calls the right 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 via the same Brevo account.
Customer portal with 2FA and invoicing
A service provider with a customer 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 the service falls back to a backup provider within 30 seconds if Brevo does not respond within the SLA.
B2B lead generation with conversational marketing
An SME without its own CRM uses Brevo CRM for lead management and the chat widget for inbound leads. A visitor who asks questions in the 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 a standard part 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 can always be traced afterwards.
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 run through which channels, and how automation and segmentation connect to your product data. Not a standalone integration, but a well-considered communication layer.
Frequently asked questions about Brevo integrations
Want to build a Brevo integration?
Talk through your situation with us. We map out the message types, channels and compliance requirements and deliver a concrete proposal, with no obligation.
Schedule a call