n8n workflows

Email verification gate in n8n — HTTP Request, branch, continue

n8n is where agency and GTM pipelines stitch scrapers, CRMs, and sequencers together. Drop Verifly in as an HTTP Request (or webhook) step after you collect emails and before you send, enrich further, or push to Instantly/Smartlead. Branch on deliverable vs undeliverable, strip disposables and role accounts, and only spend credits on addresses that hit the node.

n8n HTTP Request (single address)API
curl -X GET "https://verifly.email/api/v1/verify?email={{$json.email}}" \
  -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 n8n 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.

HTTP Request node calling GET /api/v1/verify on each list item
IF / Switch branch: deliverable continues, undeliverable drops or logs
Webhook-triggered list clean before a sequencer import
Batch node + POST /api/v1/verify/batch for chunked CSV hygiene

Where Verifly sits in an n8n outbound flow

A common agency graph: trigger (schedule / webhook / Google Sheets) → collect or enrich emails → Verifly HTTP Request → IF on result → write survivors to CRM or sequencer → optional Slack alert on undeliverable rate. The verify step is the cheapest place to kill bad guesses before they burn domain reputation or Instantly/Smartlead capacity.

Verifly returns deliverable / undeliverable / risky plus disposable, role, and catch-all flags as JSON. Map those fields in the HTTP Request node, then use an IF or Switch node so only the paths you want continue. Credits are pay-as-you-go from $2/1k down to $0.60/1k and never expire.

Wire it as an HTTP Request (or webhook) node

Add an HTTP Request node. Method GET, URL https://verifly.email/api/v1/verify?email={{$json.email}}, header Authorization: Bearer vf_…. Enable “Include Response Headers and Status” only if you need them; parse the JSON body for result, disposable, role, and catch_all. For webhook-driven cleans, accept a list payload, Split In Batches, verify each item (or call batch), then Merge.

  1. Mint a free Verifly API key (vf_…) — trial credits included.
  2. Add HTTP Request after your email collector / enrichment node.
  3. IF / Switch: continue when result is deliverable (optionally keep risky/catch-all).
  4. Push survivors to Instantly, Smartlead, HubSpot, or Sheets; log rejects.
Batch-verify a chunk from n8n
curl -X POST "https://verifly.email/api/v1/verify/batch" \
  -H "Authorization: Bearer vf_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{"emails":["alex@acme.com","a.smith@acme.com","asmith@acme.io"]}'

Why n8n builders prefer pay-as-you-go verify

Self-hosted and cloud n8n workflows often run bursty client campaigns: quiet for weeks, then a 40k-row list on Monday. Monthly verifier seats bill the quiet weeks. Verifly packs are prepaid credits with no expiry, so one pool covers every client workflow on the same instance.

Questions, a dedicated client key, or help wiring the IF branch: hello@veriflyemail.com — that is the only Verifly contact route.

FAQ

Frequently asked questions

Does Verifly have a native n8n node?

Use the built-in HTTP Request node (or a webhook + Function). That is the supported path — same Bearer API as Clay, Zapier, and custom scripts. See also /n8n-email-verification.

How do I branch on Verifly results in n8n?

After the HTTP Request, add an IF or Switch on {{$json.result}} (or your mapped field). Route deliverable to the send/CRM path; send undeliverable/disposable to a log sheet or drop them.

Can I verify a whole Google Sheet or CSV from n8n?

Yes. Read rows, Split In Batches, call POST /api/v1/verify/batch for chunks up to 100, or the async bulk endpoint for larger jobs (up to 1,000,000). Write results back to the sheet.

What about catch-all / risky results?

On a fresh sending domain, exclude them in the IF node. On a warmed domain you can keep them and watch bounce rate. Verifly flags catch-all and risky explicitly so you can choose per workflow.

Is there a free way to test the workflow?

New accounts get free trial credits. Run the HTTP Request on 20–50 sample emails, confirm the JSON shape and IF branches, then buy a pack when volume ramps.

Who do I contact for n8n / agency onboarding?

Email hello@veriflyemail.com — partnerships and support only go through that address.