Request for Global 'Do Not Run' Setting for Table Rows | Clay

Request for Global 'Do Not Run' Setting for Table Rows

Others have brought this up before and I want to give it a big +1: I really want a global (i.e. per table) ‘do no run’ for rows, meaning if a certain condition is met (or not met, which is then also met… anyways…) I want to prevent anything running without having to wire the condition into each enrichment. Thanks and have a great start to y’all’s week!

17 comments

Channeled
APP
·
·
Currently, we don't have a global 'do not run' condition for entire rows. However, we offer conditional formulas that can achieve a similar result. Here's how you can implement this: 1. Use the "Run Settings" feature in each enrichment panel. 2. In the "Only run if" box, add your conditional formula. 3. Use the "Use AI" button to create conditions in plain language without complex formulas. For example, you could set a condition like "Only run if /should_run is true" for each enrichment. Then, create a column called "should_run" and set it to true/false based on your criteria. This approach allows you to control enrichments across your table without wiring the condition into each one individually. It saves credits by ensuring enrichments only run on rows meeting your specified conditions. If you need further assistance, please request human help by clicking "Talk to a person".
Sources: Guide: Ways to save Clay credits | Documentation | Clay University Conditional Formulas
Andreas W.
·
·
one example but I have so many
Bruno R.
·
·
Hi Andreas, thanks for your message - would something like a sandbox mode for testing workflows make sense to address the request you're detailing here? Or is this request more so related to a specific state the table is in which should freeze the run conditions as a consequence? Curious to hear more about this point!
Andreas W.
·
·
hm, more like decision tree stuff, like if this is an attribute (e.g. invalid domain), then don’t ever do any further work on the row
Andreas W.
·
·
does this help what I mean?
Bruno R.
·
·
I see, something like "pause row if condition 1 is met"!
Andreas W.
·
·
yeah!
Andreas W.
·
·
so many applications
Bruno R.
·
·
Thanks Andreas, will take note of this - I agree that this is an interesting suggestion!
🙌1
Channeled
APP
·
·
Channeled
APP
·
·
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
Andreas W.
·
·
Just sending this table is a very good example. I’m adding a bunch of individual conditionals here https://app.clay.com/workspaces/271254/workbooks/wb_CVbFZ7aDfyxq/tables/t_RVanwVcS6RQp/views/gv_b6RfqYotW9X5
Andreas W.
·
·
This should be a CRM routine so the invalid domains don’t even get in here, but overall this is a great example where this would be super helpful to have per-row conditionals
Bruno R.
·
·
I see, thanks for the practical example Andreas! Adding to the internal request.
1
Channeled
APP
·
·
Channeled
APP
·
·
Thank you so much for sharing your feedback Siya V.!
Siya V.
·
·
Ah damn! Sorry guys, clicked it by mistake as i was looking at this thread