Request for Wait/Delay Feature in Salesforce Record Lookup Action

Beau M. · 2025-12-03T19:19:54.340Z

Not sure if this has already been a suggestion, but adding in a wait/delay feature would be super helpful. Context: I'd like to be able to run a salesforce record lookup action after a 20 minute delay, so that our other systems that are updating the account owner field outside of clay have time to run and update before my record lookup action runs, so that it identifies the new account owner correctly.

Request for Wait/Delay Feature in Salesforce Record Lookup Action | Clay

9 comments

· Sorted by Oldest

Clay Support
APP
·
·
Hi there, thanks so much for sharing this! We’ll be passing your feedback along to our product team, and any additional context you can provide will help us prioritize with your needs in mind as we shape the roadmap.
Want to chat with someone on the team? Feel free to hit the button below!
Clay Support
APP
·
·
Andrew W.
·
·
Beau M. https://medium.com/@batikan/how-to-add-delays-to-clay-and-why-i-built-delayclay-d8f754099c4d
Andrew Q.
·
·
Hey Beau! Thanks for reaching out. This is something our team is aware of. Temporarily though we don't support 20 minute delays, I would incorporate a tool like Postman for delayed responses.
Batıkan E.
·
·
DelayClay doesn't support 20 minutes of delay (unless you add 15 chained columns 😄 ) but 20 minutes is very long time for just updating an account owner in CRM Beau M. 🤔 what are you using for updating the account owner? feel free to DM me.
Luca P.
·
·
Hey Beau, just checking in! How did things go? Let me know if there's anything else I can do here to assist. :)
Beau M.
·
·
Thanks for all of the support here! Batıkan E. we're using LeanData flows to change the account owner, which can take up to 10 mins. So I may be able to reduce the delay to around then. At this point, what I've done is run the column on a schedule. However the shortest amount of time to re-run is an hour.
Luca P.
·
·
Hey Beau! Thanks for the update and for working through this with the team.
You're absolutely right - the hourly interval is currently the shortest timeframe for scheduled column runs. It sounds like you've found a solid workaround given the constraints! Running the Salesforce lookup on a schedule should give your LeanData flows plenty of time to complete the account owner updates.
I know it's not as immediate as a 20-minute delay would be, but the hourly schedule should at least ensure accuracy. If the timing becomes critical for your workflow, you could also explore using webhooks to trigger the lookup after LeanData completes, though that would require some additional setup on your end.
Thanks for the feedback on the delay feature - it's definitely something we're tracking as a feature request. Let me know if you run into any issues with the scheduled approach or if there's anything else I can help with! 🙌
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
·
·
Hi there, thanks so much for sharing this! We’ll be passing your feedback along to our product team, and any additional context you can provide will help us prioritize with your needs in mind as we shape the roadmap.
Want to chat with someone on the team? Feel free to hit the button below!
Clay Support
APP
·
·
Andrew W.
·
·
Beau M. https://medium.com/@batikan/how-to-add-delays-to-clay-and-why-i-built-delayclay-d8f754099c4d
Andrew Q.
·
·
Hey Beau! Thanks for reaching out. This is something our team is aware of. Temporarily though we don't support 20 minute delays, I would incorporate a tool like Postman for delayed responses.
Batıkan E.
·
·
DelayClay doesn't support 20 minutes of delay (unless you add 15 chained columns 😄 ) but 20 minutes is very long time for just updating an account owner in CRM Beau M. 🤔 what are you using for updating the account owner? feel free to DM me.
Luca P.
·
·
Hey Beau, just checking in! How did things go? Let me know if there's anything else I can do here to assist. :)
Beau M.
·
·
Thanks for all of the support here! Batıkan E. we're using LeanData flows to change the account owner, which can take up to 10 mins. So I may be able to reduce the delay to around then. At this point, what I've done is run the column on a schedule. However the shortest amount of time to re-run is an hour.
Luca P.
·
·
Hey Beau! Thanks for the update and for working through this with the team.
You're absolutely right - the hourly interval is currently the shortest timeframe for scheduled column runs. It sounds like you've found a solid workaround given the constraints! Running the Salesforce lookup on a schedule should give your LeanData flows plenty of time to complete the account owner updates.
I know it's not as immediate as a 20-minute delay would be, but the hourly schedule should at least ensure accuracy. If the timing becomes critical for your workflow, you could also explore using webhooks to trigger the lookup after LeanData completes, though that would require some additional setup on your end.
Thanks for the feedback on the delay feature - it's definitely something we're tracking as a feature request. Let me know if you run into any issues with the scheduled approach or if there's anything else I can help with! 🙌
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!