Lucile B.

Hi Yann! Sorry I missed this 🫣 The main value for me is sequencing. In my case with Intellimatch for example, records go from pending -> processing -> success. If a run triggers before everything hits "success"(which will happen if the run is immediate), you risk the next step not working as intended. So the delay gives enrichment time to complete which avoids premature downstream steps, reduces rerun loops and lowers API credit waste in some cases. Run after delay basically removes that babysitting 🚀

Michael E. There are a few strong verifiers on Clay, they mainly differ in how they treat edge cases, their real-time capabilities, and how conservative their detection is. Full transparency, I work at Findymail - so naturally biased there- but I would still recommend testing a couple on a sample of your own data and comparing bounce rates to choose 1 solid verifier rather than relying purely on "valid/risky" labels

Yes, on your table: ACTIONS -> Export -> Send table Data • Select a new table • Choose "Send row for each item in a list" • Go to Additional Data • Add nested data • Save and check your new table 🙂 Hope thats what you were looking for!

In my experience, using more than 1 verifier can be useful for some edge cases but can also backfire fast. You'll run into conflicts (especially with catch-alls) where one flags risky and another says valid based on deeper checks. Stacking tools with different detection logic doesnt always improve deliverability. Sometimes it just adds cost or makes you throw away good emails. Understanding how accurate your verifier is and how it handles catch alls is usually more useful than layering multiple ones, since validating those can open up a decent chunk of additional coverage

Someone definitely did something 😄 Thanks to whoever it was, and thanks for your help, Sayli! Have a good day too!

Mmmh I am not sure what kind of magic you used, but seems like I can edit existing columns with Delay now 😍 Thank you so much!

Here you go: https://app.clay.com/workspaces/24820/workbooks/wb_0t963odDv64obzhCUQE/tables/t_0t963oooPjPXoV7ywHg/views/gv_0t963opJ2m6NAE3TE7w

This is from a brand new HTTP column

Let me send you a screenshot (it was the very first thing I tried)