Email integration · Updated November 15, 2026

Brevo integration

Brevo can handle both your newsletter sign-ups and the email your site sends. We link your forms to Brevo lists with double opt-in, so each subscriber confirms, and route notifications through Brevo's SMTP relay or API. Brevo keeps its data in the European Union, which your privacy policy should say.

Rated 5.0 out of 5,72 Google reviews

Brevo at a glance

Connects
Sign-up forms (iframe or HTML), double opt-in, the contacts API, SMTP relay and transactional API.
WordPress
Brevo's own plugin: forms, double opt-in and SMTP for WordPress mail.
Webflow
No official app. Brevo form code in a Code Embed element.
Astro or Next.js with Sanity
A server route calls the double opt-in endpoint; site email goes through the API.
Custom software
REST API v3 with an api-key header, plus marketing and transactional webhooks.
Complexity
Low for forms. Medium for double opt-in on your own form.
Typical setup
1 day for an embedded form, 3 to 5 days for API sign-ups and site email.

How we connect Brevo

  • WordPress

    Brevo's own plugin on wordpress.org (version 3.3.6, 100,000+ active installs, updated November 5, 2026, checked November 15, 2026) builds sign-up forms with shortcodes, includes double opt-in and sends WordPress mail, contact form notifications included, through Brevo's SMTP.

  • Webflow

    We found no Brevo app in the Webflow Apps marketplace. Brevo's form builder gives iframe or HTML code for a Code Embed element, and Brevo says two forms on one page only work as iframes. Webflow's own form notifications still come from Webflow, not Brevo.

  • Astro or Next.js with Sanity

    On a headless site, an Astro endpoint or Next.js route handler takes the form and calls Brevo's double opt-in endpoint with the list, a confirmation template and a thank-you URL on your site. The person joins the list only after clicking. The same server code sends form notifications through Brevo's transactional API, with recipients set in Sanity.

  • Custom software

    The v3 API takes an api-key header. As of November 15, 2026, contact endpoints allow 10 requests a second on most plans, and transactional sending allows far more. Marketing webhooks report unsubscribes, bounces, contact updates and list additions; transactional webhooks report deliveries, bounces and blocks.

What organizations use Brevo for

  • Newsletter sign-up with double opt-in

    A Brevo form, or your own, with an unticked opt-in box. Brevo recommends repeating your consent wording in the confirmation email, so its transactional log keeps a copy of exactly what the person agreed to.

  • One provider for site email

    Contact form notifications, booking confirmations and receipts go out through Brevo's SMTP relay on port 587 or its API, from your own domain. Brevo's SMTP password is a separate SMTP key, not the API key. We keep both keys in server settings, never in page code.

  • Lists by purpose

    Brevo suggests one list per purpose and a multi-list block so people choose what they get. We map site data, such as the service or event, to contact attributes for segments.

What to watch out for

  • No CASL guidance from Brevo

    Brevo's consent guides are written for the GDPR, and we found no Brevo article on CASL. Brevo records when a contact subscribed and through which form. CASL also asks for your business name, mailing address and an unsubscribe statement on the form, and records for any implied consent you rely on.

  • EU hosting, not Canadian

    Brevo says its data is stored only in the European Union: OVH servers in France and Germany, and Google Cloud in Belgium. It's not in the US, but it isn't in Canada either. Your privacy policy names Brevo and the EU, and Quebec's Law 25 calls for an assessment before the transfer.

  • Default templates and embeds

    Brevo's default double opt-in email only works with forms built in Brevo; your own forms need a custom template with the double opt-in link. We found no accessibility statement for Brevo's forms, so we test them ourselves. As of November 15, 2026, Brevo's plugin says the free plan sends up to 300 emails a day.

Sources

Checked against Brevo's docs on November 15, 2026.

Questions about Brevo

Can Brevo forms be in French?

Yes. The form builder lets you rewrite every label and message, including success and error text. The confirmation email is a template you write, so a bilingual site gets one form and one template per language.

How does double opt-in work with our own form?

Your server calls Brevo's double opt-in endpoint with the list, a confirmation template and a redirect URL. Brevo emails a link, and only the click adds the person to the list. The template must include Brevo's double opt-in link tag.

Why send site email through Brevo?

If you already use Brevo for newsletters, notifications and receipts can share the account and sending domain. Transactional and marketing mail stay apart in the logs, and transactional webhooks tell your system when a message bounces.

Where is our data stored?

In the EU, per Brevo's help centre as of November 15, 2026: OVH servers in France and Germany plus Google Cloud in Belgium, with encrypted backups. Brevo offers no Canadian hosting.

Moving sign-ups or site email to Brevo?

List the forms you run and the email your site sends today. We'll explain how we'd connect sign-ups and whether Brevo should carry your notifications too.

Book a call