Clay template
Clay: verify the email a waterfall found before it reaches your sequencer
Add one HTTP API column after your email waterfall. Every row gets a SimpleVerifier result, and you push only rows with action send to your sequencer.
About 10 minutes to set upClay users who enrich with several finders and want one independent check before sending.
How it runs
- 1
Find
Your waterfall columns return an email.
- 2
Verify
HTTP API column calls the SimpleVerifier verify endpoint with that email.
- 3
Filter
A run condition keeps rows where action equals send.
- 4
Push
Send only those rows to Instantly, Smartlead or your CRM.
What you need
- A Clay table with an email column
- A SimpleVerifier API key from simpleverifier.com/api-keys (starts with sv_live_)
Set it up
- After your last email-finding column, click Add enrichment, choose HTTP API and open Configure.
- Set the method to GET and paste the endpoint above. Add the Authorization header. Clay stores it with the account, so you do not repeat it per column.
- Set the column to run only when the email column has a value, so empty rows do not use a call.
- Run it on 5 rows with auto-run off. Each call can take up to about 30 seconds on a slow mail server.
- Add action as its own column, then a condition so only rows where action is send continue to your sequencer push.
https://simpleverifier.com/api/v1/verify?email=/EmailIn Clay a forward slash inserts a column. Rename /Email to match your email column.
Authorization: Bearer YOUR_SIMPLEVERIFIER_API_KEYstatus
action
reason
reason_codeWhat each result means for the waterfall
| action = send | Push to the main campaign. |
|---|---|
| action = send_with_care | Separate, capped campaign, or skip. |
| action = retry_later | Run the column again later. |
| action = do_not_send | Do not push. Try the next finder in the waterfall. |
Where your judgment still matters
The check tells you whether a mailbox accepts mail, not whether the person is the right buyer. Keep your own targeting rules. Run the column on one table first and compare the result with what you use today before you switch anything.
Start with your own key
Every template calls the SimpleVerifier API with your key. Create one, then run the template on a handful of rows. To check a whole list without any setup, upload it as a CSV.
Common questions
- Is this a native Clay integration?
- No. It is Clay's HTTP API column with your own SimpleVerifier key. The full field-by-field guide is on the Clay integration page.
- Do I pay Clay credits for the check?
- Check Clay's pricing for your plan. The call itself is billed on your SimpleVerifier plan, not as a per-email Clay credit for verification.
- Which SimpleVerifier plan do I need?
- Pro is $39/month with 10,000 API and MCP calls included, then $1.50 per 1,000. Cancel anytime. Each key can make 120 calls a minute.
- What do valid, risky and invalid mean here?
- The result has a status and an action. Action send means the mail server confirmed the mailbox. send_with_care is a catch-all, role inbox or provider that hides mailbox status. retry_later means the check could not finish. do_not_send means the address will bounce or is a throwaway. Catch-all addresses are never marked valid.
Related: Clay integration, full recipe · API docs
All workflow templates · By SimpleVerifier Team