Clay tables
Email verification inside Clay — HTTP column, filter, export
Clay is where enrichment happens. Verifly is the verify step you drop in after email finders and before sequencer export. Call the Bearer API from an HTTP enrichment column, map verdict + flags, keep only deliverable rows, and spend credits only on rows that need a live check — no monthly seat tax.
curl -X GET "https://verifly.email/api/v1/verify?email={{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 Clay 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.
Where Verifly sits in a Clay workbook
A typical outbound Clay table: company → people → email permutation / finder → verify → waterfall enrich → push to Instantly or Smartlead. The verify column is the cheapest place to kill bad guesses before they burn domain reputation or sequencer capacity.
Verifly returns deliverable / undeliverable / risky plus disposable, role, and catch-all flags. Map those into Clay columns and filter in the table UI, or export survivors only. Credits are pay-as-you-go from $2/1k down to $0.60/1k and never expire.
Wire it as an HTTP enrichment column
In Clay, add an HTTP API enrichment. Point it at GET /api/v1/verify?email={{YourEmailColumn}} with Authorization: Bearer vf_…. Parse result, disposable, role, and catch_all into output columns. Run on new rows only so you do not re-spend credits on addresses you already checked.
- Mint a free Verifly API key (vf_…) — trial credits included.
- Add an HTTP API column after your email finder / permutation step.
- Map verdict + flags; filter to deliverable (optionally keep risky/catch-all).
- Export the cleaned view to your sequencer or CRM.
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 agencies prefer pay-as-you-go for Clay volume
Clay volume spikes when a new client workbook comes online and goes quiet between campaigns. Monthly verifier contracts bill the quiet weeks. Verifly packs are prepaid credits with no expiry, so one $99 / 100k pack covers a bursty quarter across every client table.
Questions or a dedicated client key: hello@veriflyemail.com — that is the only Verifly contact route.
FAQ
Frequently asked questions
Does Verifly have a native Clay integration?
Verifly works via Clay’s HTTP API enrichment (or webhook). That is the supported path — same Bearer API used by n8n, Zapier, and custom scripts. See also /clay-email-verification.
How do I avoid re-verifying the same Clay rows?
Run the HTTP column only on rows missing a prior verdict, or export unchecked emails to /api/v1/verify/batch and write results back. Credits are only charged for addresses you submit.
What should I do with catch-all / risky results in Clay?
On a fresh sending domain, exclude them. On a warmed domain you can keep them and watch bounce rate. Verifly flags catch-all and risky explicitly so you can choose per campaign.
Can I verify a full Clay CSV export?
Yes. Use POST /api/v1/verify/batch for chunks up to 100, or the async bulk endpoint for larger jobs (up to 1,000,000). Same API key.
Is there a free way to test on a sample table?
New accounts get free trial credits. Wire the HTTP column on 20–50 rows, confirm the JSON shape, then buy a pack when volume ramps.
Who do I contact for Clay / agency onboarding?
Email hello@veriflyemail.com — partnerships and support only go through that address.