Skip to main content
The Brevo integration (formerly Sendinblue) adds each respondent to a Brevo list, with full contact attribute mapping and GDPR-friendly double opt-in support.

​
What it does

  • Creates or updates a contact on the list you choose, matched by email.
  • Maps first/last name and an SMS/phone field to Brevo’s standard attributes, plus any extra attributes you define.
  • Guesses each extra attribute’s type (date, boolean, number, or text) from its name, so values are sent in the format Brevo expects.
  • With Double opt-in enabled, new contacts (not already on the list) go through Brevo’s confirmation flow using a template and redirect URL instead of being added directly.
  • Respects blacklisted contacts by default — you can allow resubscription per feed.

​
Steps to enable

1

Get your Brevo API key

In Brevo, go to SMTP & API → API Keys and copy a key.
2

Enable Brevo in Integrations

Open Integrations in the Flex Forms left rail → Brevo → paste the API key → Save.
3

Attach a feed to your form

Open the form → hub tab Integrations → add a Brevo feed → pick the list.
4

Map fields and attributes

Set the email field, optional first/last name and SMS fields, and any extra attributes using BREVO_ATTRIBUTE=field_name (attribute names are matched from Contacts → Attributes in your account).
5

Configure double opt-in (optional)

Turn on Double opt-in, pick a template containing the {{ doubleoptin }} merge tag, and set a redirect URL for after confirmation.
6

Test it

Submit the form and confirm the contact appears on the list (or receives a confirmation email, if double opt-in is on).

​
Practical tips

Only DOI templates containing the {{ doubleoptin }} tag show up in the DOI email template picker — create or edit a Brevo template to include that tag if it’s missing from the list.
Attribute type is guessed from the name: keys containing DATE become dates, BOOL/IS_/HAS_ become booleans, and NUMBER/COUNT/AMOUNT become numbers — name your Brevo attributes accordingly for automatic type handling.
Double opt-in only applies to contacts not already on the target list — an existing member of the list is updated directly, skipping the confirmation step, to avoid re-confirming existing subscribers.

​
Example

Confirm the API key was copied from SMTP & API → API Keys and hasn’t been deleted or regenerated in Brevo since.
Both a DOI template and a redirect URL are required when double opt-in is enabled — the dispatch fails outright if either is missing.
This is expected when Allow resubscription of blacklisted emails is off for the feed. Turn it on if you want previously blacklisted contacts to be added again.
Last modified on September 7, 2026