Push Only Verified Clay Rows to Instantly or Smartlead
To push only verified rows from Clay to a sequencer, give the push column a run condition: only run if the verification action is send. Only a confirmed mailbox ("Mailbox exists") gets that action. The verification column is Clay's HTTP API enrichment calling SimpleVerifier with your own key; it is not a native Clay action. The request is on the Clay integration page. This post is about the push, and it applies to any sequencer, including Instantly and Smartlead.
Step 1: verify before the push column
Order the table: find, verify, then push. Our Clay verification guide builds the column and sets the rate limit. Map action and reason to their own columns.
Step 2: gate the push
Add the run condition to whichever column sends rows out, whether that is a sequencer action, a webhook or an export:
| Condition | Result |
|---|---|
action is send |
Row is pushed to the main campaign |
| Anything else | Row stays in the table |
A filtered view alone is not a gate, because a column set to run on every row still acts on rows the view hides. Put the condition on the push column itself.
Step 3: give risky rows their own route
| action | Reasons | Route |
|---|---|---|
| send_with_care | Accepts all addresses, Role-based address | Second campaign, small batches |
| retry_later | Server would not confirm | Re-run, see retry rows |
| do_not_send | Mailbox not found, Disposable address | Not pushed |
Use a different campaign, and separate sending inboxes if you can, for the care lane. A bad segment then cannot drag down the inboxes carrying your confirmed list. Our guides to Instantly bounce rate and Smartlead bounce rate explain why sequencers pause on bounces.
Step 4: add a suppression step
Rows marked do_not_send should join a suppression list so a later import does not bring them back. See building a cold email suppression list.
If you export instead of pushing
Download the filtered view as CSV and upload it to the sequencer. For the file route, see exporting a Clay table to a clean list, cleaning an Instantly or Smartlead list and the Instantly CSV upload guide.
What this cannot do
- It does not connect to your sequencer for you. The push column and its credentials are yours to set up in Clay.
- Verified is a statement about the mailbox on the check date, not about the person's interest.
- A catch-all domain cannot be confirmed by any check and is never returned as valid.
- Sending cold email still has rules where your recipients are.
Next step
See pricing for the API calls each plan includes, or the API docs for every field.
Common questions
How do I push only verified rows from Clay to a sequencer?
Add a run condition to the push column so it only runs when the verification action is send. Rows that fail the condition never leave the table.
Does SimpleVerifier have a native Clay, Instantly or Smartlead integration?
No native action in Clay yet. The Clay setup uses Clay's HTTP API enrichment with your own key. For Instantly and Smartlead, verify before the push or export a CSV and check it first.
Where do risky rows go?
Into a separate, smaller campaign, ideally on separate sending inboxes, or into manual outreach.
Should I verify again inside the sequencer?
If the table is more than a few weeks old, re-run the verification column before pushing. A result describes the mailbox on the day it was checked.
Does verification stop all bounces?
No. A full inbox, a server problem or a job change after the check can still cause one.
Check your list before you send
Real mailbox checks over SMTP, and nothing is sent to the address. Sign in with Google and your first 100 email checks are free, no card. Plans for bigger lists are on the pricing page.