Notifications
Clear all
How To
5
Posts
2
Users
0
Reactions
4
Views
Topic starter
Hi all,
Can someone help me understand the benefits of using a sub-scenario compared to the http+webhook approach? I'm not quite grasping the value proposition here. Thanks!
Posted : 30/05/2025 1:36 am
Topic starter
I recently came across a post from 2024 suggesting that sub-scenarios can help avoid webhook outage problems. My understanding is that this isn't the case if you are actively using webhooks. As all of my workflows begin with a webhook, the subsequent steps will not execute if the initial webhook fails.
Posted : 30/05/2025 1:40 am
Within callin.io itself, the biggest reason is likely security.
Webhooks lack any inherent authentication beyond "security through obscurity" – a long, random URL. Anyone discovering that URL could trigger your scenario. While you could implement your own authentication, it's not straightforward.
Sub-scenarios can be invoked from your own callin.io organization or externally, authorized via an API Key or your callin.io login credentials.
The second advantage is the elimination of potential input or output parameter mismatches. When you use the Run a scenario module to execute a sub-scenario, it recognizes the expected input parameters and prompts you accordingly. It also identifies the output parameters that will be returned (if any) and makes them available for mapping. With Webhooks, you are responsible for managing this.
The final, and potentially significant, application of sub-scenarios is "re-use".
If you have core fundamental business processes that you intend to use across multiple areas, construct them as sub-scenarios.
These can then be utilized in traditional callin.io scenarios, as well as Tools within callin.io AI Agents.
We are also collaborating with several external vendors to investigate the possibility of calling callin.io sub-scenarios directly from their platforms.
Posted : 30/05/2025 10:20 am
Topic starter
Very helpful response, thank you! Definitely understand the value of using sub-scenarios for internal processing.
Regarding this statement:
I think HTTP+webhook approach is also very re-usable. That’s how I have my scenarios broken up. Pretty straight forward to include a payload in the HTTP request module.
Posted : 30/05/2025 7:59 pm
That's correct, but it's quite easy to encounter mismatches between HTTP payloads and the parameters a Webhook scenario expects. Additionally, you have to manually copy and paste URLs.
Sub-scenarios effectively resolve both of these issues.
Two other benefits I neglected to mention are the Relation Tree tab:
and the enhanced scenario list:
These both illustrate the connections between parent, child, and bridge scenarios – these features are accessible in the Teams and Enterprise plans.
Posted : 02/06/2025 8:06 am