Home

Clay Announcements
Clay Support
Discuss Anything
Feedback & Requests
GTM Career Advice
Introduce Yourself
Member Spotlight
Share Content and Events
Share Full-time Jobs
Share Part Time Jobs
Share Tables, Tools, and Workflows

Community Guidelines

Explore Events
Clay Cup

Powered by Tightknit

Optimizing Workflow for Delayed Webhook Processing in HubSpot | Clay

Optimizing Workflow for Delayed Webhook Processing in HubSpot

·Aug 11, 2025 12:01 PM·

Hello, I have a question delaying a table run. TLDR, I have leads coming in from a Webhook, being processed to evaluate the individual's information, and sending information to (a) a company table and (b) a Hubspot publishing table for processing. Unfortunately it takes longer to complete the company table (~2-3 min) than the Hubspot publishing table, so it's often not complete by the time I'm pushing information to Hubspot. So often it will push a partial set of information that is incomplete. Here's what I've tried:

Pushing data into the Hubspot table rather than pulling it (not possible by my read, you can only push a new row, not update a row)
Adding ~1 min of delay into the workflow by using a series of https://postman-echo.com/delay/10
Having a second "Lookup Single Row in Other Table" condition on the first "Lookup Single Row in Other Table" being complete

Unfortunately none of these have worked. Any thoughts?

8 comments

· Sorted by Oldest

Clay
APP
·
·
You can use the "Update object with HubSpot" action to update existing rows instead of only creating new ones. This action requires the HubSpot Object ID and allows you to update existing objects in HubSpot. For your workflow timing issue, consider using the "write to table" feature to push completed company data to your HubSpot publishing table only after the company table processing is finished, rather than running both processes simultaneously. The Update object action has an "Ignore blank values" option that can help ensure only complete data gets pushed to HubSpot.
Sources: HubSpot integration | Documentation | Clay University HubSpot integration | Documentation | Clay University Update object with HubSpot | Clay.com
Eric M.
·
·
https://app.clay.com/workspaces/543763/workbooks/wb_0t0ljgbXU8aH9Ygepho/tables/t_0t0ljghqCSn6Zwhvirp/views/gv_0t0ljgh6pyJSu5WdNs7
Asher
·
·
Eric M. How about splitting it into two processes?
1.
Use webhook to push the leads into a company table.
2.
Only once the above has been done processing, then do a 'write to another table', and push the data to a HubSpot publishing table?
3.
Now, everytime something is pushed to the HubSpot publishing table, you know that it's ready to be pushed into HubSpot
Muhammad S.
·
·
integrate n8n or make.com within ur workflow and it will make your life easier
Eric M.
·
·
Asher good call. Don't know why I didn't catch that! At first I was concerned about having duplicative company rows, but I should just be able to do a lookup and say if it already exists, don't push the company info into Clay again, just the individual. So basically, Webhook -> Process Individual -> Process Company (w/ a new row for each individual, just don't update to Hubspot if it's duplicative) -> Publish to Hubspot
Eric M.
·
·
Muhammad S. n8n is definitely on my list! thank you 🙂
Asher
·
·
Eric M. Indeed! The only thing to note is that there could be times (Rarely), that some type of enrichment fails when processing either the individual or company. And it may just end up being a situation where it doesn't get published to HubSpot. Would be good to do manual checks from time to time, just in case 🙂
Sayli G.
·
·
Hello Eric! Thanks for reaching out! You can add a delay to a request to httpstat.us of more than 10 sec, I think our http api are timing out after 90 sec but here you can do up to 4min by using the sleep query parameter in milliseconds. Here’s the format:
LBKS[https://httpstat.us/200?sleep=3000](https://httpstat.us/200?sleep=3000)LBKS