Start Scenario Step

Call another saved scenario as a child flow.

What it does

• Invokes a child scenario and waits for its outputs.
• Lets you pin to a specific version or always call the latest.

When to use it

• To reuse shared logic (like normalization, enrichment, notifications) across multiple parent flows.
• To keep complex projects modular—separate channel-specific or customer-specific logic into child scenarios.

How to configure

• Pick the child scenario and version (latest or a fixed number).
• Map parent data into the child’s inputs (e.g., data.customer or steps.transform.outputs.payload).
• Use the returned outputs via steps.<childStepId>.outputs.* in later steps.

Typical patterns

• Fan out to dedicated subflows per marketplace or region, then merge results.
• Call a shared enrichment routine that standardizes objects for downstream systems.
• Trigger a downstream integration maintained by another team while keeping the parent flow simple.