Webflow integration
Verify the email in every Webflow form submission
Each form submission on your Webflow site has its email checked as it comes in, so only real leads move on to your CRM, newsletter or sales inbox.
- Websites, funnels and events
- No code
- Set up in minutes
The Zap
- 1
Trigger · WebflowNew Form Submission - 2
Action · BounceIntelVerify Email Address Verdict
SafeRiskyInvalidUnknown
- Starts from
- New Form Submission
- 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 Webflow and BounceIntel already set up. Connect both accounts, check the field mapping, and turn it on.
Verify emails from new Webflow form submissions with BounceIntel
New Form Submission
Verify Email AddressOr build your own
New Form SubmissionVerify Email AddressAny Webflow 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 Webflow emails
Webflow forms are simple to publish and just as simple to abuse. Spam bots fill them in, visitors give a fake address to reach gated content, and genuine prospects mistype their domain on mobile.
Webflow stores the submission either way. Verifying the email as part of the Zap that moves it onward means your CRM and email tools only ever see addresses that can receive mail, and your sales team stops replying to leads that bounce.
03Ideas
What to do with the verdict
The check on its own changes nothing. These are the steps that make it pay off inside Webflow.
Only forward verified leads
Put a Filter on Safe to send between the check and the step that creates the contact or sends the notification. Everything else stays in Webflow's submission log.
Filter out bot submissions
Bots usually leave invalid or disposable addresses. Sending those to a separate Slack channel or sheet keeps the sales inbox for people.
Tag newsletter signups by quality
For a newsletter form, pass the verdict to your email tool as a tag, so you can see which pages bring in real subscribers.
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 Webflow
In Zapier, choose Webflow as the trigger app and pick New Form Submission, 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 Webflow 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 Webflow.
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
Webflow and BounceIntel: common questions
Does this work with every form on my site?
The trigger can watch one form or all of them. If different forms go to different places, set the trigger to a specific form and build one Zap per form.
Can I reject the submission on the page?
Not from Zapier, which runs after Webflow accepts the submission. To reject an address in the browser, the form would need to call your own backend, which calls the BounceIntel API.
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
WixWebsites, funnels and eventsWhen someone submits a form on your Wix site, their email is checked, so replies, quotes and newsletters go to people who will receive them.
Open
Facebook Lead AdsWebsites, funnels and eventsEach new lead's email is checked the moment the form is submitted, so the prefilled, forgotten and mistyped addresses are caught before your team pays attention to them.
Open
LinkedIn Lead Gen FormsWebsites, funnels and eventsEach new lead form response has its email checked the moment it arrives, so the prefilled, forgotten and outdated addresses surface before your team spends time on them.
Open
Webflow is a trademark of its owner, used here only to identify the app. BounceIntel is not affiliated with or endorsed by Webflow. The connection runs through Zapier.
Verify Webflow emails before they bounce.
Connect BounceIntel in Zapier and every new address gets a verdict your next step can act on.