Start Step
Entry point that receives the incoming payload for your scenario.
What it does
- Marks where the scenario begins and holds the data sent into the flow.
- No settings to change; it exists automatically in every scenario.
When to use it
- Always present as the first node. You cannot remove it.
- Use it as the source for values like
data.orderId,data.file, or any field defined in your input schema.
How to configure
- Define the scenario input schema in the builder; those fields become available under
data.*. - Immediately follow Start with a step that reads from
data.*—for example, mapdata.orderinto a transform or API call.
Typical patterns
- Pass the incoming payload directly to an Agent or Switch.
- Set defaults or enrich the data in the next step before branching further.