Collecting child scenario output

Features
1

It’s been about 1.5 years since this question was raised here, wondering if the situation’s changed in the meantime.

When designing a scenario chain, is it possible to collect the child scenario output? Right now it seems the only variable you can retrieve from a child scenario is its Execution ID, regardless of whatever the last module outputs.

We don’t really understand why the output isn’t available; there’s no reason not to, especially as this severely limits the usefulness of child scenarios. But maybe there’s something we’re missing?

2

Welcome to the Make community!

Instead of using the “Run a scenario” module, try using a HTTP → Webhook trigger to trigger another scenario, then use a Webhook response module to “Send” data back to the calling/parent scenario.

I’m sure others would agree that this is a nice feature to have.

You can submit this suggestion to the Idea exchange, under Platform ideas and improvements

Don’t forget to search for it first, just in case someone already suggested it, so that you don’t end up creating a duplicate.
Screenshot_2024-01-17_130153

Hope this helps! Let me know if there are any further questions or issues.

— @samliew

P.S.: Investing some effort into the Make Academy will save you lots of time and frustration using Make.

1 Like
3

Feature request posted, thanks.

1 Like
4

What happened to this request? it’s 404, but a very nice feature to have.

1 Like
5

I was recently contacted from Make that they wanted to implement this and wanted some feedback. I also think it’d be nice to have and kinda essential to complex development projects… Using webhooks & webhook responses are getting overwhelming x).

1 Like
6

Hello there, this is Vojtech, a product designer here at Make. 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 Make MCP server, allowing you to call Make scenarios from clients like Claude
  3. AI Agent tools: you can build tools for the Make 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.

1 Like