
Brevo integration
Verify Brevo contacts as they join your lists
Each contact subscribed to a list you choose has its email checked immediately, so campaigns and automations start from addresses that exist.
- Email marketing
- No code
- Set up in minutes
The Zap
- 1
Trigger · BrevoContact Subscribed to Specific List(s) Verdict
SafeRiskyInvalidUnknown
- Starts from
- Contact Subscribed to Specific List(s)
- BounceIntel step
- Verify Email Address
- You get back
- Verdict, score, reason and mailbox signals
- Zapier plan
- Any plan, including Free, for a two-step Zap
01Zaps
Start from a template
Each template opens in Zapier's editor with Brevo and BounceIntel already set up. Connect both accounts, check the field mapping, and turn it on.
Verify emails for new Brevo contacts in a list with BounceIntel
Contact Subscribed to Specific List(s)
Verify Email AddressOr build your own
Contact Subscribed to Specific List(s)
Verify Email AddressAny Brevo trigger that carries an email address can start a check. Pick it in Zapier, then add Verify Email Address and map the email.
02Why it matters
Why verify Brevo emails
Brevo prices most plans on the emails you send rather than the contacts you keep, which makes it tempting to hold on to everyone. The catch is deliverability: hard bounces are recorded against your sender, and Brevo reviews accounts whose campaigns bounce too much.
Checking contacts as they are subscribed to a list keeps bad addresses out of the sends that matter. Every campaign then goes to a list that has already been screened, and bounces stay the exception.
03Ideas
What to do with the verdict
The check on its own changes nothing. These are the steps that make it pay off inside Brevo.
Move invalid contacts to a blocklist
When the verdict is invalid, update the contact so it is blocklisted for email in Brevo. It stays in your records but is never sent to.
Record the verdict as an attribute
Create contact attributes for the verdict and score and fill them after the check. Segments can then exclude risky addresses from large sends.
Keep transactional mail flowing
Risky is not invalid. For catch-all addresses, keep sending transactional mail but hold them out of cold campaigns until they engage.
04Setup
Set it up in four steps
- 1
Get your API key
Create a key on the API keys page of your BounceIntel dashboard. Keys come with any paid plan and start with bi_live_.
- 2
Start the Zap in Brevo
In Zapier, choose Brevo as the trigger app and pick Contact Subscribed to Specific List(s), or open a template above, which does this for you.
- 3
Add Verify Email Address
Add BounceIntel as the action, connect it with your key, and map the email field from Brevo into the Email field.
- 4
Act on the verdict
Add a Filter on Safe to send, Paths on the verdict, or an update step that writes the verdict and score back to Brevo.
05Fields
What each check returns
The fields to map first. Every check also returns reason codes, a confidence level, the mail provider and the individual mailbox signals.
- Verdict
is_reachable - Safe, risky, invalid or unknown. The field to filter or branch on.
- Score
score - 0 to 100. Worth writing back so lists and reports can sort by it.
- Safe to send
safe_to_send - One true or false value, ready for a Filter step.
- Reason
sub_reason - Why the verdict was chosen, in plain words.
- Disposable address
is_disposable - A throwaway inbox from a temporary mail service.
- Role account
is_role_account - A shared inbox such as info@ or sales@ rather than a person.
- Catch-all domain
smtp_is_catch_all - The server accepts every address, so the mailbox cannot be confirmed.
- Did you mean
domain_suggestion - A corrected domain when the address looks like a typo, such as gmial.com.
06Questions
Brevo and BounceIntel: common questions
Does it matter if Brevo charges per email rather than per contact?
The saving is in reputation more than in plan size. Every hard bounce counts against your sender whichever way you pay.
Which lists should the trigger watch?
Pick the lists that collect new signups. Lists you import in bulk are better checked as a file in the BounceIntel dashboard before the import.
How many BounceIntel credits does this use?
One credit for each address checked. A Zap that runs 300 times a month uses 300 credits, and Zapier counts its own tasks separately.
Do I need a paid BounceIntel plan?
The Zap connects with an API key, and keys come with any paid plan, monthly or a one-off pack. The 100 free credits on signup can be used in the dashboard to test verdicts on your own addresses first.
More integrations
Other apps teams pair with it
MailchimpEmail marketingEvery address that joins your audience is checked on arrival, so invalid and throwaway subscribers are dealt with before a campaign is sent to them.
Open
ActiveCampaignEmail marketingEach contact added to a list gets its email checked straight away, so your automations start with addresses that can receive them.
Open
KlaviyoEmail marketingWhen a new event comes in, the profile's email is checked, so welcome, browse and cart flows only send to addresses that exist.
Open
Brevo is a trademark of its owner, used here only to identify the app. BounceIntel is not affiliated with or endorsed by Brevo. The connection runs through Zapier.
Verify Brevo emails before they bounce.
Connect BounceIntel in Zapier and every new address gets a verdict your next step can act on.