<steps>

<steps> is the required container for a workflow's executable business DAG.

Why use it

Use it to make the workflow's sequence and structural control flow visible in document order.

Common use cases

• Run sequential durable steps.
• Combine steps with choices, parallel groups, forks, and approvals.
• Define the main route that produces the workflow result.

Syntax

<steps>
  <step id="prepare">
    <script>return { ready: true };</script>
  </step>
  <step id="finish">
    <script>return context.steps.prepare;</script>
  </step>
</steps>

Rules and behavior

• Every runnable workflow contains exactly one <steps>.
• It accepts no attributes and must contain one or more flow items.
• Valid direct items are <step>, <parallel>, <choose>, <switch>, <fork>, and <approval>.
• Document order creates sequential dependency and output visibility.

Related documentation

• Steps and scripts
• Control flow