Scenario Outputs and Synchronous Subscenarios in Callin.io

I'm utilizing them extensively, eliminating the need for HTTP/webhook scenario chaining with subscenarios.

I'm utilizing subscenarios as they contain variables that I need to manage across multiple executions and reuse in different scenarios.

I'm finding the current flat list of scenarios and subscenarios a bit challenging to navigate. It would be beneficial to have a folder-like structure that displays parent scenarios with their child scenarios indented underneath.

Are there any other enhancements you're considering?

Hi, I'm looking to replace HTTP/webhook scenario chaining with sub-scenarios, but it appears that a sub-scenario cannot return any data. How have others managed this?

Hi Mikael, and welcome to the community!

At present, the sole method for scenarios to transmit data back to other scenarios involves utilizing a webhook trigger alongside a webhook response module.

However, we will soon be introducing a native platform capability that will build upon the existing Subscenarios functionality.

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?

1. You can define scenario outputs in the ‘Scenario inputs and outputs’ panel
2. New ‘Return output’ module that allows you to return data from a scenario
3. New ‘Call a subscenario’ module with ‘Wait for subscenario output’ settings
4. New ‘Start a subscenario’ module for better scenario inputs mapping

Why is it important?

1. Synchronous subscenarios: you can break down large and complex scenarios into small and reusable pieces that return data back to the parent scenario
2. 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
3. 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.

Hello everyone, for some reason, I'm not seeing the "Scenario output" tab.

Also, the button on hover displays "Scenario inputs" instead of "Scenario inputs and outputs"... am I overlooking something?

image711×462 36.7 KB

Hello, scenario outputs should now be available in your callin.io account. Could you please double-check it and let me know if you can access it?

Hi everyone! I'm really impressed with this new feature and am in the process of migrating all my workflows to adopt this structure, as it's incredibly powerful for handling conditionals and routing. I do have one significant concern, however: I'm unable to store failed executions, which prevents me from implementing error handling. I sincerely hope you can find a solution for this, as it's a major drawback.

I just came across this discussion and wanted to offer my perspective:

i) I appreciate the ability to include collections within scenario inputs. This allows for structures like:

{
"company":  {
  "name":"..",
  "email":".."
  },
"projectManager":  {
  "name":"..",
  "email":"..."
  }
}

This way, you avoid lengthy variable names like projectManagerName and companyName. However, when utilizing these collection variables in a scenario, you can only select 'company', and then you must use:

get(company,'name')

While this works for a few attributes, it's more cumbersome than necessary!

ii) Scenario Input Queues
There have been instances where I need to process hundreds of PDFs, for example, but doing so in parallel would exceed API rate limits. With scenario outputs, you can wait for one process to finish before starting the next. However, this becomes problematic if the total processing time exceeds 40 minutes (the maximum scenario execution time). In such cases, I resort to using webhooks to queue the items, ensuring they are processed sequentially.

iii) I agree about the need for handling failed executions. Webhook executions remained in the queue for retries, but this is not the case for sub-scenarios.