Recipe
Zapier outline: verify before the next action
A four-step Zap blueprint you can rebuild in minutes: trigger → Webhooks by Zapier GET verify → Filter on deliverable → CRM or sequencer. Download the outline as JSON or Markdown.
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 verify outline
Use Verifly when you need a simple API, predictable pricing, and clean JSON results before emails hit your product, CRM, or campaign tool.
The four steps
1) Trigger with an email field. 2) Webhooks by Zapier GET to /api/v1/verify. 3) Filter/Paths: result == deliverable. 4) Downstream CRM, sequencer, or email.
Assets: /samples/zapier-verify-outline.json and /samples/zapier-verify-outline.md.
- Store vf_… as a Zapier secret.
- Add Webhooks GET with Authorization Bearer secret.
- Filter early so test Zaps do not burn credits on bad paths.
- Use a staging key for drafts; prod key for live Zaps.
Batch option
Code by Zapier can POST /api/v1/verify/batch with up to 100 emails. For larger jobs use async bulk — see /docs/examples.
PAYG fits irregular Zaps
Zaps do not fire on a monthly calendar. Verifly packs never expire and only spend when a Zap verifies. Contact: hello@veriflyemail.com.
FAQ
Frequently asked questions
Is there a native Zapier app?
Webhooks by Zapier or Code steps against the public REST API are enough for production gates. See /use-cases/zapier.
Where are the downloads?
/samples/zapier-verify-outline.json and /samples/zapier-verify-outline.md.
Zapier vs n8n vs Make?
Same Verifly API. Prefer Zapier for SaaS glue, n8n for self-hosted control, Make for visual scenarios.
Ready to wire this?
Start free with 100 credits, mint a vf_ API key, and paste the recipe above. Buy a pack only when you need more — credits never expire.