Would love to help you fix your webhook workflow. I run an automation studio called Automation Jinn where we help companies automate their processes and increase efficiency.
I am a Make advanced certified with a background in computer science so quite comfortable in integrating API and custom code. Would love to talk more about the project
Hey @D_F, I see the issue: the webhook is firing, but routing breaks due to mapping order, weak validation, and missing guardrails. I can quickly trace the execution path, fix filters/mappings, add proper error handling, and stabilize the flow without redesigning it. I’m available to start immediately and can explain every fix clearly. Schedule a call here to discuss how to solve this.
Hello @D_F , 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.com issue I handle.
I can jump in immediately to diagnose where the webhook → API flow is breaking (mapping, filters, execution order), fix the routing logic, and add proper validation and error handling so it’s stable and production-safe — without rebuilding the scenario.
I work fast, document what I change, and explain the reasoning clearly so the flow stays maintainable after the fix.
If you’d like, we can do a quick chat or +234 904 684 2148 or you can share the scenario details and error logs, and I’ll get started right away
This sounds like a classic orchestration issue rather than a need for a rebuild. When webhook intake works but routing fails downstream, it’s usually due to execution order, incomplete validation at the webhook layer, or filters firing before the data is fully normalized.
I work mainly on production grade Make.com scenarios involving webhooks, API integrations, filters, and error handling, and I’ve helped unblock similar flows where mapping and routing were breaking under real data.
Approach would be to quickly inspect the webhook payload, normalize and validate early, then fix filter logic and execution order so downstream API calls behave predictably, with proper error handling added where needed.
You can check my website portfolio for relevant examples. Happy to take a quick look and help you stabilize this. You can book a short call here or continue the discussion privately in my Fiverr workspace if you prefer.
I’ll be happy to hop on a consultation call with you or solve it for you (whatever works best).
Let me know which one works for you and we can move from there.
I would start by tracing one real webhook payload through validation, filters, mapping, API request, and error handling, then deliver a fixed scenario plus a short note explaining what was failing and how to avoid repeats.
This is a good fit for a small paid diagnostic/fix slice rather than a full rebuild.
I would treat this as a rescue scope first, not a broad automation rebuild.
For a blocked webhook to API orchestration flow, I would isolate one representative webhook payload, trace the required field map, identify the failing filter/order step, add validation and retry behavior, then prove both the happy path and the missing-data path from the run log before touching the rest of the workflow.
TinyOps Studio can quote a fixed rescue sprint for this. If it is still open, DM me one sample webhook payload, the expected API output, and the current failing module/error, and I can confirm the scope.
