Yash M.

Hi Joshua - thank you for reaching out. Happy to assist you here. I do think that the AI response shared above is the most straightforward way to achieve what you're trying to do here. It will not involve any manual work and will help bring in the enriched domains from your company table wherever there is a match between the unique identifier in the contact and company table.

If you can tell me the exact column name you want to bring in from the company table and the unique identifier to create the lookup between company and contacts table, I can share a quick loom video with you to show how this can be achieved. Let me know, thanks!

Got it - yeah that makes sense. You can already filter by last week/ month. But more flexible one click filters - I hear you. Thanks for sharing all of this!

We can confirm that our engineers have pushed a fix here. Re-running the errored cells in the Use AI column/s in your table will resolve the issue on your end. Please let us know if you have any questions or concerns. Thank you again for your patience!

We can confirm that our engineers have pushed a fix here. Re-running the errored cells in the Use AI column/s in your table will resolve the issue on your end. Please let us know if you have any questions or concerns. Thank you again for your patience!

We can confirm that our engineers have pushed a fix here. Re-running the errored cells in the Use AI column/s in your table will resolve the issue on your end. Please let us know if you have any questions or concerns. Thank you again for your patience!

Hi Nathen - thank you for writing in. Saved views that persist in the usage dashboard make a lot of sense. What do you think will be most helpful here - something similar to creating saved filter views that's possible in tables? Thanks again for sharing!

Hi Aron - thank you for writing in. It looks like the find jobs table is pulling in jobs whenever a job that fits your criteria is posted. I ran it manually now to check and it did pull in one additional row.

If you'd like to pull in more results, id recommend making your job title to include list broader and a wider range for "days since posted". I also notice that there is a limit on the maximum results. You may want to increase that as well.

Please let us know if you have more questions. Thank you!

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!

Hi Cassidy - I'm Yash and work in the CX team at Clay. Absolutely love this and totally makes sense! This is something I've personally wanted in the product for a long time. Will definitely flag it as a feature request to our engineers. Thank you so much for taking the time to share! :)

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.