Flow Orchestration
A Salesforce feature that coordinates multiple flows and user interactions into a single multi-step, multi-user business process, managing steps, stages, and assignments across teams.
Definition
A Salesforce feature that coordinates multiple flows and user interactions into a single multi-step, multi-user business process, managing steps, stages, and assignments across teams.
In plain English
“Flow Orchestration is a Salesforce feature that strings multiple flows together into one big multi-step, multi-user business process. It manages stages, assignments across teams, and coordination in ways a single flow can't do alone.”
Worked example
Marshford Capital builds a multi-week customer-onboarding process using Flow Orchestration. The orchestration spans three teams (Sales, CSM, Implementation) over four stages (Welcome → Setup → Training → Go-Live). Each stage contains multiple flows assigned to different users at different times - the Welcome stage runs a kickoff flow for the AE, then a packet-creation flow for the CSM; the Setup stage assigns a configuration flow to the implementation team. Flow Orchestration coordinates assignments, stage transitions, and approvals across the multi-step, multi-user process. A single flow can't model that breadth; orchestration is the bigger container.
Why Flow Orchestration matters
Flow Orchestration is a Salesforce feature that coordinates multiple flows and user interactions into a single multi-step, multi-user business process. It adds stages and steps on top of individual flows, letting you model processes where different users handle different parts, work is passed between teams, and the overall progress is tracked at a higher level than any single flow could. Orchestrations are built in Flow Builder using the Orchestration flow type.
Flow Orchestration addresses scenarios that single flows handle poorly: long-running processes that span multiple users, workflows where handoffs between teams are first-class concepts, and complex approval-style processes that need more structure than simple approval processes provide. Examples include employee onboarding (HR, IT, manager, new hire all have tasks), loan origination (applicant, loan officer, underwriter, funding team), and complex case workflows with multiple handoffs. Orchestrations let you model these as first-class business processes rather than trying to string together separate flows and hoping they coordinate correctly.
How organizations use Flow Orchestration
Built an employee onboarding Orchestration coordinating tasks across HR, IT, the hiring manager, and the new hire. Each stage has its own assignees, and the overall process is tracked end-to-end.
Uses Flow Orchestration for loan origination, modeling the handoffs between applicant, loan officer, underwriter, and funding team as explicit stages.
Coordinates patient intake processes with Orchestration, passing work between front desk, clinical intake, and providers with clear handoffs.
Test your knowledge
Q1. What does Flow Orchestration do?
Q2. What scenarios suit Flow Orchestration?
Q3. How does Flow Orchestration build processes?
Discussion
Loading discussion…