Zapier email verification
Validate emails in Zapier with a webhook call
Use Verifly from Zapier webhooks or code steps when you need to validate an email before creating a contact, sending a notification, or moving a lead into a campaign.
GET https://verifly.email/api/v1/verify?email={{email}}
Authorization: Bearer vf_your_api_keyReal-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 Zapier email verification workflows
Use Verifly when you need a simple API, predictable pricing, and clean JSON results before emails hit your product, CRM, or campaign tool.
No custom app needed — just Webhooks by Zapier
Zapier doesn't need a dedicated Verifly integration to verify an email. The built-in Webhooks by Zapier action can call any REST endpoint, and Verifly is a plain GET request that returns clean JSON. That means you can insert a verification step into an existing Zap between the trigger and whatever action follows, without leaving Zapier or writing a custom app.
The pattern that matters most in Zapier is the guard before an expensive or hard-to-undo action. A new Typeform response, a Facebook Lead Ad, a Calendly booking — each one can carry a fat-fingered or fake email. Once that address lands in your CRM, mailing tool, or billing system, cleaning it out later is real work. Verifying it in the Zap, before the create-contact step runs, stops the bad record from ever being written.
Zapier's Filter and Paths features then let the verdict drive the flow: only continue when the result is deliverable, or split into paths that treat deliverable, risky, and undeliverable addresses differently. Verifly's pay-as-you-go pricing keeps this practical for the low, spiky volumes that typical Zaps run at.
How to add verification to a Zap
- In your Zap, after the trigger that provides an email, add an action step: Webhooks by Zapier → GET.
- Set the URL to https://verifly.email/api/v1/verify and add a query-string param email mapped to the trigger's email field.
- Under Headers, add Authorization with the value Bearer vf_your_api_key.
- Add a Filter by Zapier step (or a Paths step) that only continues when the returned result field equals deliverable.
- Place your real action — create CRM contact, add row, send welcome email — after the filter so it only fires for verified addresses.
URL: https://verifly.email/api/v1/verify
Method: GET
Query String Params:
email -> {{trigger email field}}
Headers:
Authorization -> Bearer vf_your_api_key
// Filter step condition:
// result (Text) Exactly matches deliverable
//
// Response fields available downstream:
// result, disposable, role, catch_all, smtpFAQ
Frequently asked questions
Do I need a Verifly Zapier app to do this?
No. Use the built-in Webhooks by Zapier (GET) action. Verifly is a standard REST endpoint, so a webhook GET with a Bearer header and an email query param is all that's required.
How do I stop the Zap when an email is invalid?
Add a Filter by Zapier step after the webhook that only continues when the result field equals deliverable. Steps below the filter won't run for undeliverable or risky addresses.
Can I treat risky emails differently from bad ones?
Yes — use Zapier Paths. Route deliverable down the main path, send risky or catch-all addresses to a manual-review path (e.g. a Slack message or a separate CRM stage), and drop undeliverable ones.
Where does the API key go in Zapier?
Put it in the Headers section of the Webhooks step as Authorization: Bearer vf_your_api_key. Zapier stores the step configuration securely with your account.
Is pay-as-you-go a good fit for Zapier volumes?
Yes. Most Zaps fire in low, bursty volumes, and Verifly bills per check ($2 down to $0.60 per 1,000) with 100 free credits, so there's no monthly minimum to justify against a handful of daily leads.
What email fields does Verifly return to the Zap?
A result verdict (deliverable / undeliverable / risky) plus boolean flags for disposable, role, catch_all, and the smtp check — all usable in later Zapier filters, paths, or field mappings.