HomeUse casesAdd find and verify to a waterfall
Find and verify as one step in your waterfall
A waterfall tries one provider after another until a row has an email. Add Email Finder Verifier as one step: call find with name and domain, call verify on whatever comes back, and send only the rows with no result to your next provider.
Free while in beta. No card needed.
Key takeaways
- The job: use EFV as a step in a Clay, n8n or in-house enrichment flow.
- The result: a step that's easy to reason about, with find and verify in one place.
- The rule: rows with no email, or verified false, go to the next provider.
Last updated 16 Nov 2026
01The job
The job, and why it matters
A waterfall is a list of data providers tried in order. If provider one has no email, you try provider two, and so on. It raises coverage. It also adds cost, and a found email from any provider still needs checking.
If every provider is wired to a different verifier, the flow gets messy fast. Put one verify step at the end, and the rest stays simple.
02The workflow
How to do it with EFV
Add an HTTP step with your key
Method
GET, headerX-API-Key. Use a key just for this flow.Call find with name and domain
URL
https://api.emailfinderverifier.com/api/v1/find, withfirst_name,last_nameanddomain. You getemailandesp, oremailis null.Verify the result
For any row that has an email, call
/api/v1/verify?email=next. Branch onverified.Continue only for empty rows
Rows with no email, or
verifiedfalse, can go to your next provider. Rows withverifiedtrue stop here.Verify the next provider's result too
Run an email from any other provider through the same verify step, so one rule covers the whole waterfall.
In Clay, each call is an HTTP API column. In n8n, each is an HTTP Request node with a header credential. Test one row before you run a table.
03Results
What the results mean
| Step | Answer | Next move |
|---|---|---|
| Find | email is null |
Go to the next provider. Doesn't use your allowance. |
| Find | An email | Verify it. |
| Verify | verified: true |
Stop. This row is done. |
| Verify | verified: false |
Go to the next provider, or leave the row out. |
Verify answers also say if the domain is catch-all. Catch-all emails can come back true.
Test the two calls on one row. Free while in beta.
Sign up for free04FAQ
Questions, answered
01Is a found email verified?
No. Find and verify are two calls. Chain them, in that order.
02What are the limits?
New accounts can send one request a second and have five running at once. A 429 means you went too fast. Set a timeout of at least 60 seconds.
03Can I use it as the last step in a waterfall?
Yes. Put verify at the end, and it covers every provider's result with one rule.
04Does a find with no result use my allowance?
No. A find only counts when we return an address.
05Does it work with other workflow tools?
Yes. It's a plain HTTP request. The help center has pages for Clay, n8n, Make and Zapier.
06Can I run this at higher volume?
Each account gets 100,000 verification requests or 10,000 found emails while we're in beta. If you need more, ask in Slack.
06Keep going
Where to next
- GTM engineers and Clay buildersTwo HTTP columns in Clay or n8n: find the work email, then verify it. One key.
- AI automation agenciesAn API for your n8n and Make flows and an MCP server for your agents.
- Enrichment platforms and data productsUse EFV as one more provider step, or talk to us about running it under your own name.
- Cold email agenciesCheck each client's list before it touches a mailbox you spent weeks warming up.
06Start today
Test the two calls on one row
Sign up with email or Google. No card. Your key and a ready-made first request are waiting. Need more later? Message us on Slack.