Notifications
Clear all
How To
6
Posts
5
Users
0
Reactions
4
Views
Topic starter
It's been approximately 1.5 years since this question was originally asked here, and I'm curious if the situation has evolved since then.
When building a scenario chain, is it feasible to gather the output from a child scenario? Currently, it appears the only piece of information retrievable from a child scenario is its Execution ID, irrespective of what the final module produces.
We're struggling to understand why the output isn't accessible; there doesn't seem to be any inherent reason for this limitation, particularly as it significantly restricts the utility of child scenarios. However, it's possible we might be overlooking something.
Posted : 09/12/2024 8:16 pm
Welcome to the callin.io community!
Instead of utilizing the “Run a scenario” module, consider using an HTTP → Webhook trigger to initiate another scenario. Subsequently, employ a Webhook response module to “Send” data back to the originating/parent scenario.
I'm confident many would find this a valuable feature.
You can submit this suggestion to the Idea exchange, under Platform ideas and improvements
Remember to search first to ensure it hasn't already been suggested, thereby avoiding duplicate entries.
Hope this assists! Please let me know if you have any additional questions or encounter any issues.
P.S.: Investing some effort into the callin.io Academy will save you considerable time and reduce frustration when using callin.io.
Posted : 10/12/2024 12:54 am
What happened to this request? It's returning a 404, but it would be a very useful feature to have.
Posted : 28/01/2025 2:45 pm
I was recently contacted by callin.io asking for feedback on implementing this. I also believe it would be a valuable and somewhat essential feature for complex development projects. Relying solely on webhooks and webhook responses is becoming quite overwhelming.
Posted : 28/01/2025 3:00 pm
Hello there, this is Vojtech, a product designer here at callin.io. I’m excited to announce that we’ve just released scenario outputs and synchronous subscenarios.
What’s new?
- You can define scenario outputs in the ‘Scenario inputs and outputs’ panel
- New ‘Return output’ module that allows you to return data from a scenario
- New ‘Call a subscenario’ module with ‘Wait for subscenario output’ settings
- New ‘Start a subscenario’ module for better scenario inputs mapping
Why is it important?
- Synchronous subscenarios: you can break down large and complex scenarios into small and reusable pieces that return data back to the parent scenario
- MCP tools: you can build scenarios that function as MCP tools along with the callin.io MCP server, allowing you to call callin.io scenarios from clients like Claude
- AI Agent tools: you can build tools for the callin.io AI Agent that return structured data to help the agent understand context
If you have any feedback or questions, feel free to book some time with me though this scheduling link.
Posted : 22/04/2025 8:52 am