Webflow email verification
Verify Webflow form submissions
Webflow forms are beautiful and easy to publish, but they'll accept any email that looks like an email. Route each submission through Make, Zapier, or a serverless function to Verifly, and keep fake and mistyped addresses out of your CRM and email lists.
curl -X GET "https://verifly.email/api/v1/verify?email=submitted@example.com" \
-H "Authorization: Bearer vf_your_api_key"Real-time SMTP mailbox checks
Single, batch, and async bulk verification
Disposable, role account, and catch-all detection
Pay-as-you-go credits with no subscription lock-in
Search fit
Built for Webflow form email verification
Use Verifly when you need a simple API, predictable pricing, and clean JSON results before emails hit your product, CRM, or campaign tool.
Webflow forms collect emails but don't verify them
Webflow gives designers a fast path from layout to live form, and that form's email field does exactly one check: it confirms the value roughly looks like an address. It has no idea whether the mailbox exists. So a Webflow contact form, newsletter box, or gated-download form will happily capture "hi@gmial.com" and "nope@mailinator.com" and pass both straight into whatever the form is connected to.
Because Webflow forms usually feed something automated — a CRM via native integration, an email tool via Zapier or Make, or a webhook to your own backend — those bad addresses don't get a human review. They flow directly into sequences and lists, where they bounce, drag down your sender reputation, and quietly clutter your pipeline with leads you can never reach.
Since Webflow doesn't run server code for form logic, the fix is to insert a verification step in the automation layer. Point your Webflow form submission at a Make or Zapier scenario, or a small serverless function, call Verifly there, and branch on the verdict before the data reaches its final destination.
Add Verifly between Webflow and your CRM
- In Webflow, set your form to POST to a webhook, or connect it to a Make/Zapier scenario that triggers on new submissions.
- Get a free Verifly key at verifly.email/api/v1/autonomous/register — 100 credits, no card, no captcha.
- In the serverless function or automation step, take the submitted email and call Verifly's verify endpoint.
- If the result is deliverable, continue the flow into your CRM or email tool. If not, stop the sync or route it to a review path.
- Optionally record the flags (disposable, role) so downstream tools can filter on them.
export default async function handler(req, res) {
// Webflow posts form data as name/value fields
const email = req.body.data?.Email || req.body.data?.email
const vf = await fetch(
`https://verifly.email/api/v1/verify?email=${encodeURIComponent(email)}`,
{ headers: { Authorization: 'Bearer vf_your_api_key' } }
)
const { result, disposable } = await vf.json()
if (result === 'deliverable' && !disposable) {
// forward to CRM / ESP
return res.status(200).json({ forwarded: true })
}
res.status(200).json({ forwarded: false, result })
}FAQ
Frequently asked questions
Can I verify emails inside Webflow directly?
Not on Webflow itself — it doesn't run custom server code for forms. You add the verification in the automation layer (Make, Zapier, or a serverless webhook) that receives the submission, and call Verifly from there.
Will this block the form for the visitor?
No. The Webflow form submits and confirms to the visitor as usual. Verification happens in the webhook or automation afterward, deciding whether the data continues to your CRM — the user experience is unchanged.
Which automation tool should I use?
Any that can call an HTTP endpoint works. Make and Zapier both let you add an HTTP/webhook step to hit Verifly between the Webflow trigger and your CRM action; a serverless function gives you the most control.
How do I stop gated-download abuse?
Gated Webflow forms attract disposable emails from people who just want the file. Verifly's disposable flag lets your automation withhold the download link or tag the lead when a throwaway inbox is detected.
What if my Webflow form field isn't named 'email'?
Webflow sends fields by their name, so just read whichever field holds the address (Email, your-email, etc.) from the payload before passing it to Verifly. The verify call itself is identical.
How is Webflow email verification priced?
Verifly is pay-as-you-go: $2 per 1,000 checks down to $0.60 per 1,000 at volume, with 100 free credits and no subscription. You verify one email per submission, so cost tracks form volume.