Help me choose a way to call a subscenario

How To
1

So reading this documentation l tried to play with subscenarios.

My use case is that several scenarios will call this 1 subscenario. It’s like a lot of parents and 1 child of all those parents.

The reasoning is: I do the same thing with the same modules in many scenarios. It’s better to take those a part and make it live by its own. I know this subscenario can be called simultaneosly by multiple parent scenarios, but it should process those 1 by 1 automatically, right?

I see the old way of calling a subscenario is via make webhook / http request. So I create a make webhook and paste it in a http request of the parent scenario, ok.

Then there is the module “Run a scenario” from the “Scenario” app:

image
image789×453 56 KB

Then there is the “Make” app which uses Make API as far as I understand. It is not available on free plan (not a problem) and also has a “Run a scenario”

image
image789×453 43.4 KB

I haven’t tried these options, but from my understand the difference between the last 2 are:

  • The app “Scenario” module “Run a scenario” MUST have scenario inputs filled in and can be used on free plan.
  • The app “Make” module “Run a scenario” CAN have scenario inputs filled in and can’t be used on free plan.

My concern is that I do not have fixed scenario inputs. My various scenarios have different data to pass to this single subscenario, how can I put this other scenario variable outputs in the scenarios input?

2

Do you need to pass any info to the subscenario itself? Because neither of these modules do.

You can still use a generic HTTP module that calls a custom webhook. This way you can send whatever you need inside the body of the HTTP module.

3

Another advantage of using HTTP and Webhooks is that the parent scenario can wait for completed data to be returned.

1 Like