You build an orchestration in Flow Builder, the same place you build regular flows. Plan the stages and the underlying flows first, then assemble them. Here is the high-level path.
- Create the flows you will orchestrate
Build the screen flows and autolaunched flows the orchestration will run, and activate them. The orchestration calls these as its interactive and background steps, so they need to exist first.
- Start a new Orchestration in Flow Builder
In Setup, open Flow and click New Flow. Choose the Orchestration flow type, then pick a record-triggered start (fires on create or update) or an autolaunched start (invoked by a button, the API, or Apex).
- Add stages and steps
Add stages for each phase of your process. Inside each stage, add steps that run your flows. Set each step as interactive (runs a screen flow, needs a person) or background (runs an autolaunched flow, no person).
- Assign work and set conditions
For interactive steps, set the assignee to a user, group, or queue. Map inputs into each flow and capture outputs. Add decision steps or stage completion conditions to control the path, then activate the orchestration.
Record-triggered launches automatically on a record create or update. Autolaunched is invoked on demand by a button, Apex, or the API.
Runs a screen flow and creates a work item assigned to a user, group, or queue, surfaced in the Flow Orchestration Work Guide.
Runs an autolaunched flow with no user interaction, used for record updates, callouts, and other silent work.
Defines when a stage is done so the orchestration can advance to the next stage in sequence.
- Stages always run one at a time and in order; only steps inside a stage can run in parallel, not the stages themselves.
- An interactive step will not complete until the assigned person finishes the screen flow, so a stalled run usually means an open, unworked work item.
- Place the Flow Orchestration Work Guide component on the relevant record page, or assignees will get the email but have nowhere to do the task.
- Plan your flow input and output mappings before wiring steps; changing them later can break every downstream step that reads those values.