--- title: Scenarios slug: scenario-service image: https://make-cxp-documentation.ams3.cdn.digitaloceanspaces.com/apps-center-icons/PREVIEW_DEFAULT.png docTags: createdAt: 2025-07-07T12:44:16.662Z --- ::::VerticalSplit{layout="left"} :::VerticalSplitItem ::Image[]{src="https://api.archbee.com/api/optimize/oAyFj2GHlBeBVWF5OAir2/gta-zz-anayIE0wPJAYXX-20260119-161453.png" size="40" width="918" height="918" position="center" showCaption="false"} ::: :::VerticalSplitItem Scenarios is a built-in app for managing scenarios. With the Scenarios app in Make, you can start or call a scenario, return scenario outputs, and customize the run name. ::: :::: # Modules With the **Scenarios **app, you can use the following modules to build your scenarios. :::hint{type="info"} All **Scenarios **modules are free to use, as they do not consume [credits](docId\:hh-nrTakEqakBmg63UUiN). ::: ## Triggers ### Start scenario Starts the scenario when called by another source, and lets you receive scenario inputs. :::hint{type="info"} You should use the **Start scenario** module in a called scenario. ::: | **Field** | **Description** | | ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Receive data from another source** | Click **Add scenario inputs** to open **Scenario inputs and outputs** in the scenario toolbar.
In **[Scenario inputs](https://help.make.com/scenario-inputs-and-outputs)**, define the scenario inputs that you want to pass into this subscenario from the calling scenario:

- **Name**: The name of the input.
- **Description**: The description of the input.
- **Type**: The data type.
- **Default value**: The pre-set value when an explicit value is not specified.
- **Required**: Whether the input is required.
- **Multi-line**: Whether the input is displayed in a single line (No) or multiple lines (Yes).
:inlineImage[]{src="https://api.archbee.com/api/optimize/oAyFj2GHlBeBVWF5OAir2/0j236ucvU2VNTpJFQDfYi-20260216-154128.png" alt caption size="80" width="958" height="1326"} | ## Actions ### Call a scenario Calls another scenario from the scenario flow, and lets you pass scenario inputs and outputs between the two. All scenarios called by the **Call a scenario **module must be active and scheduled **On demand**. :::hint{type="info"} Updates to scenario inputs and outputs in subscenarios are not automatically reflected in parent scenarios. To sync changes, return to the parent scenario, open the **Call a scenario **module, and update the scenario inputs. Scenario outputs should be updated in the subsequent modules of the parent scenario ::: | **Field** | **Description** | | ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Scenario** | Select an existing scenario within your team or create a scenario.
- **Existing scenario**
Select a scenario in the dropdown. It must be active and scheduled to **On demand**.
- **Create a scenario**
Click the **Create scenario **button in the dropdown to open a configuration dialog:
**Name**: Name of the scenario (max. 120 characters)
**Description**: Description of the scenario's purpose (max. 240 characters)
**Input structure**: Input name(s) and parameters (see Start a scenario).
**Output structure**: Output name(s) and parameters. | | **Scenario Inputs** | Map the value of the input to pass into the scenario you're calling. For example, from a preceding module's output bundle or a hard-coded value (e.g., a function).
:inlineImage[]{src="https://api.archbee.com/api/optimize/oAyFj2GHlBeBVWF5OAir2/Cvi-1tbmvbzjcent6YsbW-20260120-092557.png" alt caption}
These fields are autogenerated after you define the scenario input names in the called scenario. | | **Wait for the scenario to finish ** | - Select **Yes** if the calling scenario needs to receive outputs from the called scenario to continue its run. With **Yes** selected, the module waits for the called scenario to finish its run and return output.
- Select **No** if the calling scenario doesn't need outputs from the called scenario to continue its run. With No selected, the module calls the scenario and continues its run. | ### Return output Sends the scenario's output back to the source that called it. You add this module to the end of a called scenario. | **Field** | **Description** | | ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **\[Output name]** | Click **Add scenario outputs** to open **Scenario inputs and outputs** in the scenario toolbar.
In **Scenario Outputs**tab, define the scenario outputs that you want to pass from the called scenario to the calling scenario:
- **Name**: The name of the output.
- **Description**: The description of the output.
- **Type**: The data type.
- **Default value**: The pre-set value when an explicit value is not specified.
- **Required**: Whether the output is required.
- **Multi-line**: Whether the output is displayed in a single line (No) or multiple lines (Yes).
:inlineImage[]{src="https://api.archbee.com/api/optimize/oAyFj2GHlBeBVWF5OAir2/h7hXoaeLYm2sonylnh_it-20260120-094206.png" alt caption size="40" width="614" height="1268"}
Map the value of the output to send back to the calling scenario. This value can be from a preceding module's output bundle or a hard-coded value (e.g., function).
:inlineImage[]{src="https://api.archbee.com/api/optimize/oAyFj2GHlBeBVWF5OAir2/SL2PiDZ_LVbD0LkA01B-h-20260120-094128.png" alt caption}

These fields are autogenerated after you define scenario outputs in this module's scenario, in **Scenario inputs and outputs**. | ### Customize run name Defines a custom scenario run name so you can easily identify and search for records. Add this module anywhere in your scenario to name runs conditionally based on data mapped from a preceding module. You can add it multiple times in a scenario, such as at the end of each route, to name runs based on where data is processed. You can find custom run names in the **Run name** column of the [scenario history](docId:9Z2XnH-Lyy62CFAhjFHj5). The **Customize run name** module furthest in the scenario route defines the name that appears in this table. | **Field** | **Description** | | ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Run name** | Enter a custom run name. You can map data from preceding modules to generate a unique value for each run.

For example: New contact:` recipientName`
| # Scenarios resources - Make Help Center: [Subscenarios](https://help.make.com/subscenarios) - Make Help Center: [Scenario inputs and outputs](docId:7odICud0KE9-Tr4XWUiqn)