Issue with Account Creation Timing in Salesforce Workflow

Jamie C. · 2025-12-03T22:43:14.901Z

Workflow: I am attempting to lookup Salesforce Account records, and create new accounts where one does not exist. Once this account is created, I am then looking up the newly created AccountID in a separate table where the Account creation occurs. Problem: This lookup is running before Account creation completes. I've tried various approaches to get a delay in place and have yet to have success, could use some guidance.

Issue with Account Creation Timing in Salesforce Workflow | Clay

Clay Support
APP
·
·
Use the "Only run if" condition in your lookup column's Run Settings to check that the Account creation column has completed first.
For better control, add a formula column between the Account creation and lookup steps using:
Clay.getCellStatus(#{{field_id}})
Replace {{field_id}} with your Account creation column's ID. This checks if the creation step is actually completed.
Then set your lookup column to only run when this formula column shows "completed" status. This ensures proper sequencing even if the Account creation returns no data initially. [1]
Clay Support
APP
·
·
Is that what you were looking for?
Jamie C.
·
·
Can I reference a column in a differrent table?
Clay Support
APP
·
·
Yes, you can reference columns from different tables using the Lookup Rows feature. [1]
Use either:
Lookup Single Row in Other Table for faster single-row lookups
Lookup Multiple Rows in Other Table for multiple matching records
Both actions let you specify the table to search, target column, filter operator, and row value to match. [2] This works similarly to VLOOKUP in spreadsheets for pivoting data between tables.
Clay Support
APP
·
·
Did that answer your question?
Jamie C.
·
·
I'm using the lookup row feature already. It's running before the row is done running in that spreadsheet.
Clay Support
APP
·
·
For cross-table lookups, add a formula column using Clay.getCellStatus(#{{field_id}}) to check if the source row has completed processing.
Then set your lookup column's "Only run if" condition to only execute when this formula shows "completed" status. This ensures the lookup waits for the source table row to finish before running.
Clay Support
APP
·
·
Was this helpful?
Clay Support
APP
·
·
If you still need help with ensuring your lookup runs after the account creation completes, I’m here to assist. Would you like to provide more details about your workflow or any specific issues you’re encountering?
Jamie C.
·
·
Still need some help here. I have the lookup single rows in another table running when a row sends data to another table. What I am not finding, is how to ensure that the account has finished creating in that other table. I could use some support. Table here that needs to run the lookup after a delay Table doing the account creation here.
Clay Support
APP
·
·
Got it - you need to check the status of the account creation in the other table before your lookup runs.
Create a formula column in your lookup table using:
Clay.getCellStatus(#{{field_id}})
Replace {{field_id}} with the column ID from your account creation column in the other table.
Then set your lookup column's "Only run if" condition to only execute when this formula shows "completed" status. This ensures the lookup waits for the account creation to finish processing before running.
This method works even if the account creation returns no data initially - it checks actual completion status rather than just data presence.
Clay Support
APP
·
·
Is that what you were looking for?
Jamie C.
·
·
where can I get the column ID
Clay Support
APP
·
·
To get the column ID for your Clay.getCellStatus formula:
1.
Click on the column header in your account creation table
2.
Look at the URL in your browser - the column ID appears after /columns/ in the format cl_xxxxxxxxx
3.
Copy that ID and use it in your formula: Clay.getCellStatus(#cl_xxxxxxxxx)
This will let you check the completion status of your account creation column from your lookup table.
Clay Support
APP
·
·
Did that answer your question?

23 comments