Your first 100,000 email verifications or 10,000 work emails found are on us.100K verifications or 10K finds, free.Sign up today

HomeWho it's forGTM engineers and Clay builders

Find and verify in two HTTP steps

Email Finder Verifier gives you find and verify as two plain GET requests on one API key. Drop them into a Clay table or an n8n flow, branch on a true or false answer, and move on to the next provider only for the rows that came back empty.

Free while in beta. No card needed.

Key takeaways

  • Your job: build tables and flows that end in emails you can send to.
  • The result: find and verify as two steps with one key, so a client doesn't need two accounts.
  • Time: one HTTP column takes a few minutes to set up. Test it on a single row first.

Last updated 16 Nov 2026

01The problem

Your problem, and what EFV does

Your problem What EFV does
A waterfall (a list of providers tried one after another) gets costly and the emails still bounce. Add a verify column after the find step, so only confirmed addresses move on.
A client wants find and verify in one place. Two requests on one key: find gives the email, verify gives true or false.
Catch-all domains break your filter. Every answer says if the domain is catch-all. Catch-all emails can come back verified: true.
You need to know which mail system a lead sits on. Each answer names the provider, like Google or Outlook.
Rows with no name, only a company. Find team inboxes like info@ and sales@ for any domain.

02The workflow

Build it in Clay

  1. Make a key named for the table

    In the dashboard, open API keys and create one called "Clay - client name". One key per table means you can delete one without breaking the others.

  2. Add the find column

    In your Clay table, add an HTTP API enrichment (a column that fetches data for each row). Method GET, URL https://api.emailfinderverifier.com/api/v1/find. Map first_name, last_name and domain to your columns. Add the header X-API-Key with your key.

  3. Run one row, then the rest

    Check the answer. You get email and esp (the mail provider). If there's no email, email is null and that find doesn't use your allowance.

  4. Add the verify column

    Add a second HTTP API column. URL https://api.emailfinderverifier.com/api/v1/verify?email= and insert the found email after the equals sign. Same header. Pull verified into its own column.

  5. Filter on verified

    Keep rows where verified is true. Send rows with no email, or verified false, on to your next provider if you have one.

On n8n, it's the same two steps as two HTTP Request nodes with a header credential, then an IF node on verified. Turn on batching at one item per second.

03Limits

Limits to build around

Plan the flow around these numbers. They are the real limits for new accounts.

Limit What it means for your table
One request a second Set a small batch size in Clay, or add a delay. A 429 error means you went too fast.
Five at once Don't run more than five rows at the same moment.
Some checks take several seconds Set a timeout of at least 60 seconds.
100,000 verification requests or 10,000 found emails per account Ask in Slack when a client project needs more.

04Example

Example: one Clay table, four rows

Made-up rows. The columns after "Domain" are the two HTTP API columns you add.

First Last Domain find: email verify: verified Next step
Maya Patel northwind.example maya@northwind.example true Done, send
Jordan Chen brightpath.example j.chen@brightpath.example false Next provider
Ana Ruiz quarry.example null (skipped) Next provider
Sam Okafor lumen.example sam.okafor@lumen.example true Done, send

Use a filter on verified to send true rows on, and the other rows to your next provider.

Wire it into one table first. Free while in beta, key in a minute.

Sign up for free

05FAQ

Questions, answered

01Should I run find on every row?

Only on rows with no email. Rows that already have one only need verify. A find with no result doesn't use your allowance.

02Can I use one key for every client table?

You can, but one key per table is safer. If a key leaks, you delete only that one. All keys share the same allowance.

03What does the answer look like?

Verify gives { "verified": true, "esp": "Google" }. Find gives { "email": "maya@northwind.example", "esp": "Google" }. Plain true or false, no maybe pile.

04Can I look up if a domain is catch-all before I run a table?

Yes. There's a domain lookup endpoint that returns the mail provider and whether the domain is catch-all. Looking up a domain doesn't use your allowance.

05Does it work from n8n and Make too?

Yes. It's an HTTP request with a key in a header, so any tool that can send one works. The help center has step-by-step pages for Clay, n8n, Make and Zapier.

07Start today

Wire it into your next table

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.