Clay table to email list: work emails, validation results and flags in one file
In short: Reads a Clay table CSV, finds the work email column (personal email only when asked), reads a validation column (valid, catch-all, invalid), counts rows where enrichment found nothing, merges repeats and flags role addresses, webmail and domain mismatches. Limit: Clay columns are whatever you named them; the email and validation columns are found by common names (an inferred list), so rename them if the notes say none was found.
In Clay, use Actions > Export > Download CSV and upload the file here. The work email column becomes the send address, a validation column is read (valid kept, catch-all marked risky, invalid set aside), rows where enrichment found no email are counted, repeats merge and role addresses are set aside. Then check what's left live before the sequencer.
Price: this tool is free. Checking a whole email list is from $9/mo, and the first 100 checks are free with Google, no card. See pricing
Sample result
6 Clay rows: 3 to send, 1 invalid set aside, 2 with no work email.
- Addresses
- 3 to check
- Valid
- 2
- Catch-all
- 1
What this means for you
Catch-all results pass most validation columns; this one is marked risky.
- Work email found by name
- Validation column read
- Blank enrichments counted
- Personal email optional
- Clay
- Table
- CSV
By SimpleVerifier Team · Last updated · Runs in your browser; nothing you paste is sent to us
How do I check the Clay emails before they reach the sequencer?
- Download the clean list here.
- Upload it at /verify. Every address gets a live mailbox check, and valid, risky and invalid download as separate files; catch-all domains are marked. The first 100 email checks are free with a Google sign-in, no card.
- Push only the valid file to the sequencer, or verify inside Clay with an HTTP API column on the next run.
How do I turn a Clay table CSV into a clean email list?
- In Clay, open the table, filter the view to the rows you want with the email and validation columns visible, then Actions > Export > Download CSV.
- Upload the CSV here, or paste it. The email, name, company, website and status columns are found by name.
- Choose what to set aside: the validation column's invalid addresses and role addresses (on to start), accept-all and unverified addresses, personal webmail.
- Download the clean list and the set-aside file, each with a flags column (role, webmail, possible typo, domain differs from the company website).
Example
- You enter
- A Clay table CSV with 6 rows:
Work Emailfilled on 4,Personal Emailon 1, one row with neither, and anEmail Validationcolumn reading valid, catch-all and invalid. - You get
- 3 in the list (2 valid, 1 catch-all marked risky), 1 set aside as invalid, and 2 rows counted as having no work email. Ticking the other-email option adds the Gmail row, flagged as personal webmail.
- Limits
- Runs in your browser with no row cap; an uploaded file can be up to 25 MB.
Which column is the email?
Clay tables have no fixed columns. The tool looks for a work email first (Work Email, Email, Found Email, Find Work Email), then a personal email only if you tick the option. The source_column in the download says which column each address came from.
A validation, verification or status column is read as valid, catch-all (risky) or invalid. Cells where the enrichment didn't run come out blank in Clay's CSV; those rows are counted as having no email.
Can I verify inside Clay instead?
Yes: an HTTP API enrichment column can call a verification API for each row. The guide to verifying emails in Clay sets it up with SimpleVerifier's API. This page is for a table you've already exported.
Who uses this tool, and for what?
- GTM engineers
- Check a waterfall's output before it goes to Instantly, Smartlead or HeyReach.
- Agencies
- Hand a client a clean send file and a set-aside file with reasons from one Clay table.
- Founders
- Drop role inboxes and blank enrichments from a Clay list without writing formulas.
What can’t this tool tell you?
- Clay columns are whatever you named them; the email and validation columns are found by common names (an inferred list), so rename them if the notes say none was found.
- It can't tell which addresses have a working inbox today, or which domains accept every address; that needs a live mailbox check.
- A lead database list is cold: nobody on it asked to hear from you. The tool doesn't make it compliant; follow the rules where your recipients are.
Common questions
- Why does it say Lead list export rather than Clay?
- Clay tables have the column names you gave them, so there may be nothing that marks the file as Clay. The reading is the same either way.
- Can it tell which domains are catch-all?
- Not from the file alone. It reads the vendor's own accept-all or catch-all label where the export has one. Whether a domain accepts every address only shows up in a live check, which /verify runs and marks.
- Is my lead list uploaded?
- No. The file is read in your browser. Nothing is sent unless you choose to check the addresses afterwards.
Sources
A tidy list can still be full of dead addresses.
Extracting, deduplicating and syntax checks all work on the text of an address. None of them can tell whether the mailbox exists. Only the server that hosts it can answer that, through an SMTP check, and that is what the paid product does.
- Upload the cleaned file as it is: CSVs up to 100,000 rows
- A real SMTP mailbox check on every row, with catch-all detection
- Small list? Starter at $9/mo covers 2,500 emails a month, cancel anytime
Plans from $9 a month, cancel anytime, no contract. Sign in with Google and your first 100 email checks are free, no card. The free tools stay free either way.