Zapier automation

Zapier: verify emails before the next action fires

Zapier connects forms, CRMs, sheets, and sequencers — but it will happily pass undeliverable addresses downstream. Insert Verifly as a Webhooks by Zapier or Code step so only deliverable emails reach HubSpot, Salesforce, Instantly, Smartlead, or Gmail. Prepaid credits, never expire.

Get 100 free credits Read API docs

Zapier Webhooks GET verifyAPI

GET https://verifly.email/api/v1/verify?email={{email}}
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 Zapier 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.

Typeform / Webflow form → Verifly → HubSpot/Salesforce only if deliverable

Google Sheets new row → Verifly → Instantly/Smartlead lead create

HubSpot contact create → Verifly → branch + set properties

Nightly Sheet/CRM export → batch verify → filtered write-back

Where Verifly sits in a Zap

Trigger (form, Sheet, CRM) → Action: Webhooks by Zapier (GET verify) or Code by Zapier → Filter / Paths on result=deliverable → downstream CRM, sequencer, or email. Fail closed on undeliverable and disposable.

For multi-row cleans, collect emails and call POST /api/v1/verify/batch (≤100) from a Code step, or push large jobs to async bulk and poll.

Build the verify step

Store vf_… as a Zapier secret. Prefer Webhooks by Zapier for single-email paths. Parse JSON: result, disposable, role, catch_all. Use Zapier Filter or Paths so non-deliverable rows never hit Instantly, HubSpot enrollment, or Gmail.

Create Verifly API key; add to Zapier as secret.
Add Webhooks by Zapier GET to /api/v1/verify?email=…
Map Authorization: Bearer {{secret}}.
Filter: only continue when result equals deliverable.

Batch from Code by Zapier (sketch)

const emails = inputData.emails.split(',');
const res = await fetch('https://verifly.email/api/v1/verify/batch', {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${process.env.VERIFLY_API_KEY}`,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({ emails }),
});
return await res.json();

PAYG fits Zapier volume

Zaps fire irregularly. A monthly verifier seat bills quiet weeks; Verifly credits only move when a Zap actually verifies. Packs never expire across clients and environments.

Assets also live under /downloads and /integrations. Contact: hello@veriflyemail.com.

FAQ

Frequently asked questions

Is there an official Zapier app?

You can use Webhooks by Zapier or Code steps against the public REST API today. Distribution assets under /integrations document the pattern; a native app is not required for production verify gates.

How do I avoid burning credits on test Zaps?

Use Zapier’s test with a known address, then turn on Filters early. Staging with a dedicated Verifly key keeps prod credit pools clean.

Zapier vs Make vs n8n?

Same Verifly API. Prefer Zapier for simple SaaS glue, Make for visual scenarios, n8n for self-hosted control. See sibling use-case pages for each.

Can agents call the same API?

Yes — REST or hosted MCP at /mcp. Zaps and agents can share one credit pack.

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.

Start free · 100 credits View pricing API docs