# Webhook redirection issue

**URL:** <https://community.make.com/t/webhook-redirection-issue/103189>\
**Category:** Questions\
**Tags:** webhooks\
**Created:** [February 10, 2026, 1:52pm UTC](https://community.make.com/t/webhook-redirection-issue/103189 "2026-02-10T13:52:03Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Damir](https://avatars.discourse-cdn.com/v4/letter/d/7993a0/32.png) [@Damir](https://community.make.com/u/Damir)\
**Post date:** [February 10, 2026, 1:52pm UTC](https://community.make.com/t/webhook-redirection-issue/103189/1 "2026-02-10T13:52:03Z")

</div>

### 🎯 What is your goal?

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.

---

<div class="post-metadata">

**Author:** ![Stoyan\_Vatov](https://avatars.discourse-cdn.com/v4/letter/s/5daacb/32.png) [@Stoyan\_Vatov](https://community.make.com/u/Stoyan_Vatov)\
**Post date:** [February 10, 2026, 1:57pm UTC](https://community.make.com/t/webhook-redirection-issue/103189/3 "2026-02-10T13:57:56Z")

</div>

Hey Damor,

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.

---

<div class="post-metadata">

**Author:** ![Damir](https://avatars.discourse-cdn.com/v4/letter/d/7993a0/32.png) [@Damir](https://community.make.com/u/Damir)\
**Post date:** [February 10, 2026, 2:00pm UTC](https://community.make.com/t/webhook-redirection-issue/103189/4 "2026-02-10T14:00:57Z")

</div>

Hi Stoyan,

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

---

<div class="post-metadata">

**Author:** ![Stoyan\_Vatov](https://avatars.discourse-cdn.com/v4/letter/s/5daacb/32.png) [@Stoyan\_Vatov](https://community.make.com/u/Stoyan_Vatov)\
**Post date:** [February 10, 2026, 2:18pm UTC](https://community.make.com/t/webhook-redirection-issue/103189/5 "2026-02-10T14:18:54Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![David\_Zisner](https://avatars.discourse-cdn.com/v4/letter/d/3d9bf3/32.png) [@David\_Zisner](https://community.make.com/u/David_Zisner)\
**Post date:** [March 11, 2026, 12:57pm UTC](https://community.make.com/t/webhook-redirection-issue/103189/6 "2026-03-11T12:57:46Z")

</div>

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.

Came across a short video that walks through exactly how this breaks: [https://youtu.be/THbOXcWu-bI](https://youtu.be/THbOXcWu-bI)

---

<div class="post-metadata">

**Author:** ![Make\_Bot](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/make_bot/32/14661_2.png) [@Make\_Bot](https://community.make.com/u/Make_Bot)\
**Post date:** [June 9, 2026, 12:03pm UTC](https://community.make.com/t/webhook-redirection-issue/103189/7 "2026-06-09T12:03:19Z")

</div>


