Finish Step

Define the final outputs returned from the scenario.

What it does

• Marks the end of a path and shapes the response your scenario returns.
• Maps values from prior steps or the original input into the final result object.

When to use it

• Always present as the last node on every execution path.
• Use multiple Finish steps when different branches need different outputs.

How to configure

• Map outputs you want to expose: reference prior data (e.g., steps.create.outputs.id, data.orderId) or set literals.
• Keep the output structure consistent with your API contract or consuming system.

Typical patterns

• Return a success flag plus IDs created upstream.
• Return transformed objects (e.g., harmonized order/product) for downstream use.
• Summarize per-item results from a Split (counts, errors, combined payloads).