Hey @Dan_Espy , I see you need help completing the retrieval step so your webhook can return Clay’s enriched result reliably. I can fix the record lookup (ID mapping or search), add the webhook response for real-time output, and implement fallback handling when no result is found. I’ve built similar Clay + webhook workflows and can resolve this quickly. Happy to review your current setup and finish it end-to-end. schedule a call with me here to discuss this further.
Hello @Dan_Espy , welcome to make.com community, I have worked and have experience with Make.com and l will love to collaborate with you on this you can schedule a call Here and you can checkout my upwork profile Here, for my pastworks and certifications
This is exactly the kind of Make with Clay integration I work on regularly, and I can help you finish this cleanly and reliably.
From your description, everything up to “Create Record” is working, so the issue is mainly around retrieving the enriched row correctly and responding to the original webhook, which is a common sticking point.
Here’s how I would approach it:
Correct Retrieval of the Enriched Record
Capture and store the Clay Record ID immediately after “Create a Record”.
After the 30-second Sleep (or preferably using a polling/check loop for reliability), use:
Either “Get a Record” (if ID is available), or
Search/List Records filtered by Record ID or unique URL.
Map the “Result” column from the enriched row once Clay AI has finished processing.
If needed, I’ll also replace the static 30-second wait with a smarter loop that checks whether the enrichment field is populated — this avoids returning empty results.
Webhook Response (Critical Step)
Add the “Webhook Response” module at the end of the scenario.
Structure the JSON response cleanly so your frontend can immediately display the result.
Ensure the webhook only responds once (no duplicate executions).
Error Handling / Default Result
Add a filter condition:
If “Result” is empty or not found → return structured “Default Result” JSON.
If found → return enriched result.
This ensures your website never receives a 500 or timeout error.
Optional improvements (if useful):
Add execution timeout safeguards.
Add logging for failed enrichments.
Optimize response time so the user experience feels instant.
I can review your current scenario (since it’s 70–80% done), finalize the retrieval logic, implement the webhook response properly, and make the flow production-safe.
Yes, this can absolutely be sorted out. It looks like the main issue is retrieving the enriched record properly and setting up the webhook response the right way.
I’ve worked on similar webhook → AI enrichment → real-time response setups before. I can help fix the Record ID mapping (or use a Search module if that’s more reliable), add the proper Webhook Response module, and set up fallback handling so your site always gets a clean result instead of an error.
I’d be happy to take a look at what you’ve built and help you wrap this up quickly.
You’re very close. The retrieval plus webhook response step is usually where these Clay flows break.
I can help you properly map the Record ID, retrieve the enriched row reliably, and structure the webhook response so your site receives the result cleanly with fallback handling.
Quick questions:
1. Are you saving the Record ID from the initial create step for later lookup?
2. Is the 30 second wait fixed or does enrichment time vary?
3. What exact JSON structure does your frontend expect back?
Let’s move this to Fiverr so we can review your scenario privately and fix it end to end without exposing workflow details publicly.
Looking forward to hearing from you soon Dan!!!
Website Portfolio: Check out related automation samples here from my previous works.
Book a Call: Schedule a 20 minutes walkthrough call meeting here: Adjust to your timezone)
Fiverr Workspace: Reach out to me here (PS: I am available 24/7)
Hi, yes, I can help you finish this Make.com workflow.
Right now the scenario is doing the right thing up to the point where Clay finishes enrichment, but it’s missing the step where we reliably re-fetch that same row and pull the value from the Result column. I’ll fix the retrieval (using the Record ID if available, or a search if needed), then add the Webhook Response at the end so your website immediately receives the answer and can display it.
I’ll also add a simple fallback: if Clay hasn’t produced a result yet (or the result is blank), the scenario will return a Default Result instead of throwing an error.
I am Priyanshu Kumar, Founder of Evara AI (incubated at IIT Bhubaneswar). Finishing partially-built workflows that are stuck on the last critical steps is something I do frequently, and your setup is a pattern I recognize well.
Looking at your description, the 70-80% you have built is solid – the webhook trigger, Clay record creation, and the sleep module are all correct pieces. The retrieval step is where most people get stuck because Clay does not always populate the Result column within a fixed timeframe, and the Record ID mapping between the Create module output and the subsequent Get/Search module needs to be precise.
Here is what I would do to complete this:
- Map the Record ID from the Clay “Create a Record” output directly into a “Get a Record” module (preferred over Search for reliability and speed)
- Replace the fixed 30-second sleep with a polling loop that checks if the Result column is populated, with a maximum timeout – this prevents both premature reads and unnecessary waiting
- Add the Webhook Response module at the end that returns the enriched data in the format your frontend expects
- Implement error handling with a Router: one path for successful results, one path that returns a clean default response if Clay has not finished enrichment or returns empty
I have a couple of slots open this week. Feel free to DM me here and I can review your current scenario and scope the completion work.
Check my profile:
Book a quick call: