Why Was Conditional Logic Removed from Find People Search Column?

Oliver M. · 2026-01-27T16:50:36.738Z

Hey team - How come conditional logic was removed for find people search column? i feel like its made it worse now - it was super handy having run conditions here

Why Was Conditional Logic Removed from Find People Search Column? | Clay

11 comments

· Sorted by Oldest

Clay Support
APP
·
·
Conditional logic (the "Only run if" feature) is still available in Clay - it hasn't been removed from find people search columns. [1] You can add conditional runs to control when enrichments execute by going to your column settings, clicking "Edit column," then enabling "Only run if" under Run settings.
To set it up: enable "Only run if" in your column settings, click "Use AI" to write the formula in plain language, or write it manually using column references, then save. For example, you could set conditions like "only run if LinkedIn URL exists" or "only run if company size > 50."
The conditional runs work like if-else statements - if your condition is true, the enrichment runs; if false, it doesn't. [2] You can reference dynamic variables from your workflow and use comparison operators to create your conditions.
What specific conditions were you trying to set up in your find people search column?
Clay Support
APP
·
·
If you still need help with setting up conditional logic in your find people search column, I’m here to assist. Would you like to share more about the specific conditions you’re trying to implement or any issues you’re encountering?
Oliver M.
·
·
not true - can I talk to a person
Clay Support
APP
·
·
I understand your concern and will connect you to a human teammate who can assist you further.
Clay Support
APP
·
·
Our support team has got your message and we'll get back to you soon!
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!

image.png(93 kB)
Aditi S.
·
·
Hi Oliver - thanks so much for reaching out. Unfortunately, you are not able to add run conditions to this column type. The column is linked to your company table and is based on the inputs coming through there.
Oliver M.
·
·
Thanks - how come it changed? It was much better before to have conditional logic when running people searches Aditi S. Seems like a step back there
Yash M.
·
·
Hi Oliver - thank you for reaching out here. Curious, how you were using the run condition setting in this column earlier? What was the goal you were trying to achieve with it?
For context - the Update people search column in this case is one that is auto-generated when you trigger a find people search (to a new table). This column primarily acts as the connection between your company/ accounts and people table. In the previous version of this column, while the UI allowed users to add run conditions, these run conditions were unable to actually control the output of the people search/ table itself.
The only way to control the results of the people search is from within the people search source settings (by clicking on "Edit source" in the first column of the people search table). And so the run condition functionality over here was only adding more clutter without providing actual value. Which is why we have now deprecated it altogether. I hope this makes sense but please let us know if you have any questions or concerns.
Oliver M.
·
·
It was helpful because you could run multiple people search from a companies table into 1 people table and divide it up based on classifications in the companies table. For example last week we had classified a companies table into 10 buckets. Each bucket depended on the size what the company focused on amd what they did etc. Based on that our people search would be different for each bucket - and rather than create 10 people tables, it's much easier and better to run a conditional formula to only X search if they are in bucket 1, 2 etc Just one example but I think it helped a tonne having the conditional formula so you could easily split searches into one table
Yash M.
·
·
Got it - appreciate you taking the time to explain the use case here. By any chance would you be able to share an existing table where you had built this flow in the past?
I ask because the way our people search is set up (even when there was an option to add run conditions to the update people search column), it will always query over the entire list of companies in a company table that you set as the input source for a people search. As I mentioned above, the run condition in the update people search column in the company table wouldn't allow you to control your people search.
The recommended approach to achieve your goal (run multiple people searches based on different company segments such that all people records are pulled in the same people table) is as follows: https://www.loom.com/share/b95978f5f0da47beb83bc8edb0ec482c
Please let me know if you have any other questions or concerns. I hope this helps!
Clay Support
APP
·
·
We haven't heard back from you here, so we're going to go ahead and close this thread out.

Still need help here? Reply back and someone will jump back in.

Have a question thats not related to this thread? We recommend kicking off a new ticket in the support channel!

Clay Support
APP
·
·
Conditional logic (the "Only run if" feature) is still available in Clay - it hasn't been removed from find people search columns. [1] You can add conditional runs to control when enrichments execute by going to your column settings, clicking "Edit column," then enabling "Only run if" under Run settings.
To set it up: enable "Only run if" in your column settings, click "Use AI" to write the formula in plain language, or write it manually using column references, then save. For example, you could set conditions like "only run if LinkedIn URL exists" or "only run if company size > 50."
The conditional runs work like if-else statements - if your condition is true, the enrichment runs; if false, it doesn't. [2] You can reference dynamic variables from your workflow and use comparison operators to create your conditions.
What specific conditions were you trying to set up in your find people search column?
Clay Support
APP
·
·
If you still need help with setting up conditional logic in your find people search column, I’m here to assist. Would you like to share more about the specific conditions you’re trying to implement or any issues you’re encountering?
Oliver M.
·
·
not true - can I talk to a person
Clay Support
APP
·
·
I understand your concern and will connect you to a human teammate who can assist you further.
Clay Support
APP
·
·
Our support team has got your message and we'll get back to you soon!
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!

image.png(93 kB)
Aditi S.
·
·
Hi Oliver - thanks so much for reaching out. Unfortunately, you are not able to add run conditions to this column type. The column is linked to your company table and is based on the inputs coming through there.
Oliver M.
·
·
Thanks - how come it changed? It was much better before to have conditional logic when running people searches Aditi S. Seems like a step back there
Yash M.
·
·
Hi Oliver - thank you for reaching out here. Curious, how you were using the run condition setting in this column earlier? What was the goal you were trying to achieve with it?
For context - the Update people search column in this case is one that is auto-generated when you trigger a find people search (to a new table). This column primarily acts as the connection between your company/ accounts and people table. In the previous version of this column, while the UI allowed users to add run conditions, these run conditions were unable to actually control the output of the people search/ table itself.
The only way to control the results of the people search is from within the people search source settings (by clicking on "Edit source" in the first column of the people search table). And so the run condition functionality over here was only adding more clutter without providing actual value. Which is why we have now deprecated it altogether. I hope this makes sense but please let us know if you have any questions or concerns.
Oliver M.
·
·
It was helpful because you could run multiple people search from a companies table into 1 people table and divide it up based on classifications in the companies table. For example last week we had classified a companies table into 10 buckets. Each bucket depended on the size what the company focused on amd what they did etc. Based on that our people search would be different for each bucket - and rather than create 10 people tables, it's much easier and better to run a conditional formula to only X search if they are in bucket 1, 2 etc Just one example but I think it helped a tonne having the conditional formula so you could easily split searches into one table
Yash M.
·
·
Got it - appreciate you taking the time to explain the use case here. By any chance would you be able to share an existing table where you had built this flow in the past?
I ask because the way our people search is set up (even when there was an option to add run conditions to the update people search column), it will always query over the entire list of companies in a company table that you set as the input source for a people search. As I mentioned above, the run condition in the update people search column in the company table wouldn't allow you to control your people search.
The recommended approach to achieve your goal (run multiple people searches based on different company segments such that all people records are pulled in the same people table) is as follows: https://www.loom.com/share/b95978f5f0da47beb83bc8edb0ec482c
Please let me know if you have any other questions or concerns. I hope this helps!
Clay Support
APP
·
·
We haven't heard back from you here, so we're going to go ahead and close this thread out.

Still need help here? Reply back and someone will jump back in.

Have a question thats not related to this thread? We recommend kicking off a new ticket in the support channel!