Add newsletter signups to a Brevo list
Every footer signup becomes a Brevo contact in your newsletter list, with the topics they chose already attached.
New newsletter signup submitted
Create or update a contact in a Brevo list
One-directional. A submission triggers the action — nothing is written back into your form.
A signup box lives in a footer or a sidebar and asks for almost nothing: a first name, an email, maybe the subjects someone cares about. The work starts after the submit button, when that person has to reach the list you actually send from.
This flow closes that gap. It suits anyone running a regular send — a studio newsletter, a product changelog, a shop's monthly note — who would rather not paste addresses into Brevo by hand. Double opt-in still runs on Brevo's side if you have it switched on.
Setting it up
- 1
Publish your newsletter signup form and put it where people meet it: a footer block, a slide-in, or an inline embed at the end of a post.
- 2
In Brevo, create the list this form should feed, for example Newsletter, and note its name so you can pick it in the Zap.
- 3
Add a text attribute in Brevo for the subjects a subscriber picks, such as TOPICS, before you build the Zap so the mapping has somewhere to land.
- 4
In Zapier, create the Zap with the New Submission trigger and select your newsletter signup form as the form to watch.
- 5
Choose Brevo's create or update contact action, so a returning subscriber updates the existing record instead of failing on a duplicate.
- 6
Map Email Address to the contact email, First Name to FIRSTNAME, and Topics You're Interested In to your TOPICS attribute.
- 7
Set the list to your Newsletter list and add a static SOURCE value in the Zap, such as site footer, so these subscribers are distinguishable from imported ones.
- 8
Submit the form once yourself, check the contact and its topics in Brevo, then switch the Zap on.
What maps where
Using the Newsletter Signup Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Brevo |
|---|---|
| First Name | FIRSTNAME attribute on the Brevo contact, used in the email greeting |
| Email Address | The contact's email address — the value Brevo deduplicates on |
| Topics You're Interested In | A TOPICS text attribute used to segment the list before a send |
Variations worth knowing
If your topics map to genuinely different sends, add a filter step in Zapier after the trigger and branch on Topics You're Interested In. Each branch adds the contact to a different Brevo list, rather than one list carrying an attribute you have to segment on later.
Some people leave the name blank. Set a default value in the Zapier mapping — there works fine — so a Brevo template that opens with the FIRSTNAME merge tag never sends a greeting with a hole in the middle of it.
If something isn't arriving
The list field in the Brevo action step was left empty, which creates the contact without a subscription. Reopen the action, pick your Newsletter list explicitly, then replay the task from Zapier's history so the existing contact is added.
Multi-select answers pass through as a single comma-separated value. Either keep the Brevo attribute as text and build segments with a contains condition, or add a Zapier formatter step to split the value before the Brevo action runs.
Frequently asked questions
Does this work with Brevo's double opt-in?
Yes. The Zap adds the contact to the list, and if double opt-in is switched on for that list, Brevo sends its own confirmation and holds the subscription until the person clicks. The confirmation comes from Brevo, not from the form.
What happens if someone signs up twice?
The create or update action matches on email address, so a second submission updates the existing Brevo contact instead of making a duplicate. Any new topics overwrite the previous attribute value, which means you always segment on their most recent answer.
If someone unsubscribes in Brevo, does the form know?
No. The connection runs one way: a submission triggers an action in Brevo, and nothing is written back into the form. Brevo stays the record of who is subscribed, and it keeps an unsubscribed contact out of your sends by itself.
Related automations
- Add webinar registrations to a Brevo reminder list
Each registration becomes a Brevo contact on the list for that session, with company and job title already filled in.
- Log support requests on the Brevo contact
A help request creates or updates the Brevo contact and records what was asked, so follow-up email sends from one profile.
- Send gated guide downloads to a Brevo list
The download form adds the reader to a Brevo list with attributes for the asset and the date they asked for it.
- Start a Brevo nurture workflow for demo requests
A demo request creates the Brevo contact, records what the prospect wants to solve, and enters them into your welcome automation.
- Store survey scores as Brevo contact attributes
Post-purchase survey answers update the Brevo contact with a score and a comment you can segment a follow-up send on.
- Add buyers to a customers list after each order
Each order form submission adds the buyer to a Customers list in Constant Contact for updates and repeat-purchase emails.
Build the form first
The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow.
Start free