My goal is to alleviate the pressure on my main scenario (current have more than 50+ workflows with 300+ modules). Adding new scenarios just adds more complexity and slow management.
What is the problem & what have you tried?
The problem is, how do I redirect my payload (simple text) after webhook A (let’s call it) received, to another brand new scenario? Call Scenario module doesn’t work because I cannot send the processed response to the same webhook A from the brand new scenario.
I tried with HTTP to call to redirect my payload to the webhook C (in the brand new scenario) but this also doesn’t work. I need my brand new scenario to return the response to my main webhook that received the original payload.
If this sounds confusing let me visualise it below:
SCENARIO A: Webhook A ----> Modules ----> Webhook B
SCENARIO B (brand new scenario): Webhook C -----> Modules ---- Webhook D
Because my front end calls the Webhook A and it needs to send the response back from that scenario unfortunately. This is one of the Make’s limitations, in my mind.
I just want to alleviate the stress from my main scenario. Anybody has any solutions?
Error messages or input/output bundles
I don’t have any error messages because there is no mechanism how to solve this issue.
You can use the call a subscenario module and send data over it, then from that scenario, you can return data back to the main scenario so it can call the original webhook back.
This doesn’t solve my problem - it introduces less modules in the main scenario but I want to redirect some of the payloads (filtering by keywords) to the brand new scenario
If I do as you suggested I would still adding modules in the main scenario
If you want to return the response to the same webhook, then it needs to happen in the same execution. You cant do it from a different scenario.
Also what do you mean it doesn’t remove modules? You replace an entire flow with a single module and have that flow happen within the subscenario instead. Can you share some screenshots of what you are building and what you are trying to offload to a subscenario?
One specific pain that doesn’t get mentioned enough: webhook URLs used as click destinations.
You build a clean scenario - form submits, webhook fires, CRM updates, the works. Then you realize the person who clicked is sitting there staring at a raw “Accepted” response while your scenario runs on their browser. They bounce. Your analytics show zero conversions. The scenario ran perfectly.
The fix is architectural - the webhook needs to fire server-side before the redirect, not client-side as the destination. User lands instantly, scenario runs in the background, no one waits for anything.
What is your goal?
What is the problem & what have you tried?
Error messages or input/output bundles