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.
New ebook download form submitted
Add the contact to a Brevo list and set custom attributes
One-directional. A submission triggers the action — nothing is written back into your form.
A guide behind a form is only useful if you know which guide each reader took. Six months of downloads with no asset name attached leaves you with one undifferentiated list and no honest reason to email any of it.
Recording the asset at the moment of download fixes that. Content marketers reach for this when the same list feeds several reports, benchmarks and templates, and the follow-up email has to match what the person actually read.
Setting it up
- 1
Publish the download form on the landing page for that one guide, so a single form maps cleanly to a single asset.
- 2
In Brevo, add the attributes the follow-up depends on: ASSET for the guide name and DOWNLOAD_DATE as a date attribute.
- 3
Create the Brevo list that collects downloads and build the triggered email that carries the download link to the guide.
- 4
In Zapier, point the New Submission trigger at the download form and pull a sample submission through.
- 5
Add Brevo's create or update contact action, mapping Work Email as the identifier and Full Name into FIRSTNAME.
- 6
Set ASSET as a static value in the Zap — the guide's title — rather than from a form field, since this form is already asset-specific.
- 7
Map Zapier's submission timestamp to DOWNLOAD_DATE, so the attribute reflects when the request arrived rather than when you built the Zap.
- 8
Add the contact to the download list, test with your own address, confirm the guide email arrives, then enable the Zap.
What maps where
Using the Lead Generation Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Brevo |
|---|---|
| Full Name | FIRSTNAME on the Brevo contact |
| Work Email | The contact's email address, and where the download link is sent |
| Company Name | A COMPANY attribute on the profile |
| What are you most interested in? (check all that apply) | An INTERESTS attribute used to choose the next email |
| How did you hear about us? | A SOURCE attribute for channel reporting in Brevo |
Variations worth knowing
If you would rather not run a list per asset, keep a single Downloads list and let ASSET do the sorting. Brevo segments on attribute values, so a condition of ASSET equals Pricing Benchmark is a perfectly workable audience for a follow-up send.
Add a date attribute such as LAST_DOWNLOAD and let every submission overwrite it. Read alongside ASSET, it tells you who is still reading and who stopped after their first guide, which is enough to build a re-engagement segment.
If something isn't arriving
One Zap with a static asset name is now serving several landing pages. Duplicate the Zap for each guide and point every copy at its own form, so the static value stays true to the page the form sits on.
Brevo's triggered email fires on its own condition, usually list entry. Check that the Zap really adds the contact to that list, and check the address is not on Brevo's blocklist from an earlier bounce or unsubscribe.
Frequently asked questions
Can the form deliver the file itself?
No — the form collects the request and Brevo sends the email carrying the download link. A File Upload field takes a file in from the person filling the form rather than serving one back out, so host the guide where you host it today and paste that link into the Brevo template.
Do I need a separate form for every guide?
It is the simplest way to keep the asset name honest, and forms are unlimited during early access. One form per guide also gives you clean per-asset numbers in responses without filtering a shared submission list afterwards.
Does a download count as marketing consent?
That is your call under GDPR, not something the Zap decides for you. Many teams add a consent checkbox to the form and filter on it in Zapier, so only people who opted in ever reach the marketing list.
Related automations
- 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.
- 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.
- 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