// sales engagement and cold email
Via APIClay email verification with pingutil
Clay tables are where many teams find and assemble emails before sending rows to a sequencer, which makes them the right place to verify. Add an HTTP API enrichment column that posts each email to pingutil, return status, reason and score as columns, and only push rows marked valid.
Where it connects: Clay HTTP API enrichment column (POST to pingutil, field paths to return, run condition)
What goes wrong without it
- Our Clay waterfall finds an email for most rows, but found does not mean deliverable.
- We push rows from Clay into the sequencer automatically, so a bad email goes straight to a send.
- We need to know which rows are on catch-all domains before we choose a campaign.
What you can do with Clay and pingutil
Verify found emails in the table
An HTTP API column calls /v1/verify for each row and returns status, reason and score as their own columns.
Gate the push to your sequencer
Set the push action's run condition to status equals valid, so only verified rows go to Smartlead, Instantly, lemlist or others.
Classify the domain fast
A second HTTP API column on /v1/lookup with skip_enrichment true returns category (free, disposable, company) and email_signals in milliseconds.
Set it up
- 1
In Clay, save a header account with Authorization: Bearer pk_live_... so the key is not visible in the column.
- 2
Add enrichment, choose HTTP API, set Method POST and Endpoint https://pingutil.com/v1/verify.
- 3
Set the JSON body to {"email": "/Work Email"} using your email column reference, in quotes.
- 4
Set field paths to return: status, reason, score, did_you_mean, checks.catch_all.
- 5
Set the rate limit to 1 request per 1000 ms to stay under pingutil's 60 requests a minute, and a run condition so empty emails are skipped.
- 6
Test on one row, then run the column and use status in the run condition of your sequencer push.
{
"method": "POST",
"endpoint": "https://pingutil.com/v1/verify",
"header_account": "pingutil (Authorization: Bearer pk_live_your_key)",
"body": {
"email": "/Work Email"
},
"field_paths_to_return": ["status", "reason", "score", "did_you_mean", "checks.catch_all"],
"rate_limit": { "requests": 1, "duration_ms": 1000 },
"run_condition": "Work Email is not empty",
"next_column": "Push to sequencer: only run if status = valid"
}What to do with each result
| pingutil result | Action in Clay |
|---|---|
| status: valid | Allow the sequencer push column to run. |
| status: invalid | Try the next email source in your waterfall, or drop the row. |
| status: risky, checks.catch_all: true | Route to a separate catch-all campaign or a LinkedIn-first play. |
| status: unknown | Re-run the column on these rows later. |
| did_you_mean is set | Treat as a hint for manual review; do not replace a found email automatically. |
Limits to plan for
- pingutil allows 60 requests per minute and 300 verified addresses per day (3,000 a month) per account; a large table needs several days or Enterprise limits. Those are Free plan limits.
- Clay HTTP API columns call one row at a time, so /v1/verify/batch is not used here.
- Clay requires string column references in the JSON body to be wrapped in quotes; an unquoted reference fails to parse.
Clay documentation
Clay is a trademark of its owner. This integration uses Clay's documented extension points; it is not an official Clay app.
Common questions
- Does Clay have a pingutil integration in its list?
- No. You connect it through Clay's generic HTTP API enrichment column, which works with any REST API.
- Do failed pingutil calls stop the table?
- No. A row whose call errors or hits a limit just has empty result columns. Keep the push condition on status = valid so those rows wait instead of being sent.
Stop bad addresses in Clay today
Sign in with your email, create an API key and paste it into the step above. Test on a few real addresses first: the live demo shows exactly what your Clay setup will receive.