Make.com scenarios
Make.com webhook / HTTP verify gate
Make (formerly Integromat) is where agencies stitch forms, CRMs, and sequencers. Add Verifly as an HTTP module (or custom webhook) after you collect emails and before you create CRM records or push to Instantly/Smartlead/lemlist. Branch on deliverable, drop disposables and role accounts, and only spend credits on addresses that hit the module.
curl -X GET "https://verifly.email/api/v1/verify?email={{1.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 Make.com 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 Make scenario
A common agency scenario: Webhook / form / Google Sheets → collect emails → Verifly HTTP → Router on result → create HubSpot/Pipedrive contact or push to Instantly → optional Slack on undeliverable rate. The verify module is the cheapest place to kill bad guesses before they burn domain reputation.
Verifly returns deliverable / undeliverable / risky plus disposable, role, and catch-all as JSON. Map those fields in the HTTP module, then Router 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 (or webhook) module
Add an HTTP module. Method GET, URL https://verifly.email/api/v1/verify?email={{email}}, header Authorization: Bearer vf_…. Parse JSON for result, disposable, role, catch_all. For webhook-driven cleans, accept a list, Iterator over items (or batch), verify, then Aggregate survivors.
- Mint a free Verifly API key (vf_…) — trial credits included.
- Add HTTP after your email collector / enrichment module.
- Router: continue when result is deliverable (optionally keep risky/catch-all).
- Push survivors to Instantly, Smartlead, HubSpot, or Sheets; log rejects.
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 Make builders prefer pay-as-you-go verify
Make scenarios 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 scenario on the same organization.
Questions or help wiring the Router: hello@veriflyemail.com — that is the only Verifly contact route. Full recipe also lives on the blog under Make.com webhook verify.
FAQ
Frequently asked questions
Does Verifly have a native Make app?
Use the built-in HTTP module (or a custom webhook). That is the supported path — same Bearer API as n8n, Clay, Zapier, and custom scripts. See also /make-email-verification and the Make blueprint under /integrations.
How do I branch on Verifly results in Make?
After the HTTP module, add a Router (or filter) on result. Route deliverable to the send/CRM path; send undeliverable/disposable to a log sheet or Error Handler.
Can I verify a whole Google Sheet or CSV from Make?
Yes. Read rows, Iterator (or Array aggregator), call POST /api/v1/verify/batch for chunks up to 100, or the async bulk endpoint for larger jobs. Write results back to the sheet.
What about catch-all / risky results?
On a fresh sending domain, exclude them in the Router. On a warmed domain you can keep them and watch bounce rate. Verifly flags catch-all and risky explicitly.
Is there a free way to test the scenario?
New accounts get free trial credits. Run the HTTP module on 20–50 sample emails, confirm the JSON shape and Router filters, then buy a pack when volume ramps.
Who do I contact for Make / agency onboarding?
Email hello@veriflyemail.com — partnerships and support only go through that address.