Creating a Sequential Linear Workflow for Data Management | Clay

Creating a Sequential Linear Workflow for Data Management | Clay

Clay Support
APP
·
·
You can create a fully sequential workflow using conditional runs and the Clay.getCellStatus() formula. Here's how to build it:
Step 1: Set up sequential dependencies
For each column, use "Only run if" conditions in Run Settings to check that the previous step completed
Use this formula in a helper column: Clay.getCellStatus(#{{field_id}}) to check completion status
Step 2: Create the sequence
1.
People Search → runs first
2.
Status Check Column → uses Clay.getCellStatus() to verify people search completed
3.
First Lookup → "Only run if" the status check shows completion
4.
Claygent Decision Maker Search → "Only run if" lookup has 0 results OR no final email
5.
Second Lookup → "Only run if" Claygent found results
6.
Generic Email Search → "Only run if" second lookup has no final email
Step 3: Add delay columns
Insert 10-second delay columns between steps if needed for processing time
This approach eliminates manual intervention and ensures each step only runs when conditions are met. The Clay.getCellStatus() function is key for tight dependency control . [1] [2]
Clay Support
APP
·
·
Was that helpful?
Petar R.
·
·
I was told by Bo (. that getcellstatus won't work for update people search enrichment. He suggested something that makes sense I was just not able to build it without more information. Can you connect me to the human agent please?
Clay Support
APP
·
·
I understand, and I’ll connect you to a human agent who can assist you further.
Intercom
APP
·
·
Clay Support is sharing a file with you.
Our support team has got your message and we'll get back to you soon! We're currently outside of our standard office hours (9 AM to 9 PM EST, Monday through Friday), so it may take a little longer for us to respond.
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!
Loading attachments
Petar R.
·
·
Can someone get back to me on this today?
Yash M.
·
·
Hi Petar - happy to help you optimize here. In order to provide the right recommendation it would be good to know what the final goal here is? What is the final data point you're trying to achieve for these leads that you find?
Overall your current workflow makes sense to me without having context on your end goal. If there are specific columns or formulas that are causing the flow to break, could you point those out so I can take a deeper look there? Thank you!
Petar R.
·
·
The end goal is to maximize the number of emails found (whether it's with email finding tools or claygent searching for generic emails). The current issue is - I need to manually do 2 Lookups after the people search has finished. I want to achieve: automatic workflow where I just need to add the leads and turn all tables on.
Petar R.
·
·
Bo (. and Aditi S. had an idea how to do this.
Yash M.
·
·
Gotcha. Instead of the current flow what if you tried something along these lines?
Start with a list of companies - company table
Find people at these companies - people table 1. In the people search filters here you can specify the persona you want to find at these companies (c-suite, founders, etc).
Once you have these people in people table 1 - you can find emails for all them using an email waterfall
This flow will help achieve a few things:
1.
You wont have to depend on a claygent column to find key people at a company - the find people search will do that for you
2.
You wont need multiple lookups to go back and forth between tables
3.
Using email waterfalls will always outperform a claygent scrape when it comes to finding emails
Let me know if this doesn't work or if I'm missing something here and I'll be happy to think this through further. Thank you!
Petar R.
·
·
Hey Yash M. so what you described is the first part of my workflow. After I used find people I want to use Claygent to find top decision makers for those companies that clay's people search didn't find. Then I want to use Claygent after this step, to find generic website emails for everyone else that's not found. Makes sense? Bo (. can you please jump in ? He was spot on but I need just few more pieces of information to finalize this.
Yash M.
·
·
Hi Petar. Thanks so much for your patience here. In that case, you could also try the in-line "Find people at company" enrichment (instead of the find people source). This will allow you to have a find people column in your company table itself. This column will find people and store all of them in the same cell for each row. You can then add a claygent column to extract the decision maker out of the people found for each company. Finally, run the email waterfall only on the decision maker in this table.
For the rest of the people found, you can send them as their own individual rows into a new table using send table data action. These can then be enriched via email waterfall in the new table. Let me know if this sounds like a smoother way to achieve your goal? Thanks!
1
Petar R.
·
·
This sounds doable! Let me test it!
Yash M.
·
·
Sounds good! I'll leave this conversation open for now so you can get back to us in case you have any questions!
Petar R.
·
·
Yash M. the only problem with this is that Find People enrichment costs credits and Find People Source is free to find people. Is there any way to do it with find people source? or free alternative?