A guide to using flow orchestration in Salesforce

Automations are meant to make things easier. But consider this: You build an automation that looks perfect at first glance, but it falls apart because it relies on a human to do something at some point.

Someone may need to review a document offline, get approval from another department, or wait for a signature. The process then stalls, and your automation breaks.

The Salesforce Admin Blog captures this problem:

“Admins like you know workflow requirements are becoming increasingly complex. Simple processes have evolved to span multiple users or departments. You may have to wait days, weeks, or months between each stage of a workflow.”

As developers and admins, we are often asked to patch these gaps with validation rules, tasks, and custom Apex. But there is a cleaner way to handle these long-running, multi-user situations.

In this post, we’ll break down what flow orchestration is, how it works, and how to use it to organize business processes.

What is flow orchestration?

Flow orchestration is a process automation tool that allows you to coordinate multiple flows and users into a single, unified business process.

Unlike standard flows that usually run from trigger to finish in one go, an orchestration is designed to “pause” and wait. This might mean waiting for a manager to click approve or for an external system to send back data.

What is Salesforce?

Salesforce is a leading customer relationship management (CRM) platform. It helps businesses connect with their customers across sales, service, marketing, and more. Automation is a core part of the platform, allowing teams to reduce manual data entry and speed up service.

Flow orchestration represents the next level of this capability, specifically for complex, long-running processes.

Overview of flow orchestration in Salesforce

To understand orchestration, you need to look at the standard Salesforce flow, which—like a record-triggered flow—is linear. It triggers, runs through its logic, and finishes. It’s excellent for immediate actions like updating a field or creating a task.

But business processes rarely happen in seconds. They are more likely to happen over days or weeks. Flow orchestration is the state manager for these longer processes.

Think of it as the project manager of automation. It does not necessarily do the work itself. Instead, it delegates tasks to different people and systems at the right time.

How it works

An orchestration coordinates a series of stages and steps. It functions as a parent flow that manages child flows. It can pause and wait for a user to complete a screen flow, then wake up and trigger a background system update, then pause again for a different user in a different department.

Also, it maintains the state of the record throughout this entire journey, so you always know exactly where the process is.

Without orchestration, you are often forced to stitch processes together using wait elements or scheduled paths.

Why it’s important

Without orchestration, you are often forced to stitch processes together using wait elements or scheduled paths. These methods are fragile and hard to visualize.

If a user delays their task by three days, a standard scheduled path might fire incorrectly or fail. Orchestration solves this by waiting indefinitely for specific criteria to be met before moving forward.

It gives you a unified view of the entire life cycle of a record, allowing you to track exactly whose court the ball is in.

Key features of Salesforce flow orchestration

To build an orchestration, you need to know its building blocks:

Stages

These are the major phases of your process. For a hiring process, your stages might be “application review,” “interview,” and “offer.” Each stage contains multiple steps and includes entry and exit criteria.

Steps

Inside each stage, you have steps, which are the actual actions.

• Interactive steps: Assign a screen flow to a specific user or queue.
• Background steps: Run an autolaunched flow instantly without user input.

Decisions

Just like in standard flows, decision elements let you branch logic (e.g., if a deal is under $50k, you might skip the “VP approval” stage).

Work guide

This is a Lightning component you add to record the page. It shows the assigned user exactly what they need to do right now, eliminating the need to hunt through tasks.

Approval orchestrations

Salesforce has introduced approval orchestrations, which replace legacy approval processes with a flow-based approach. These support complex branching, custom notifications, and group approvals.

Benefits of using flow orchestration in Salesforce

Moving your complicated logic into orchestration offers clear advantages over scattered workflow rules or custom Apex.

Salesforce has improved monitoring capabilities with on-canvas insights and runtime tracking that can help identify bottlenecks.

1. Unified visibility and monitoring

You see the entire process in one canvas. Instead of searching through multiple automation tools, everything is visualized in a single orchestration builder. At runtime, you can check the orchestration instance to see exactly which stage is active.

Salesforce has improved monitoring capabilities with on-canvas insights and runtime tracking that can help identify bottlenecks.

2. Automated flow creation

Einstein AI can automatically build flows based on your instructions. You simply describe what you want to automate, and it generates the flow for you. This helps save time and improve accuracy in flow creation.

3. Reduced maintenance overhead

Before orchestration, teams often built complex Apex triggers or scheduled jobs to monitor record states. Orchestration handles the waiting and state management natively, reducing the amount of custom code you need to maintain and test.

How to set up flow orchestration in Salesforce

Setting up an orchestration requires a shift in how you think about automation. You are building a map of a business process:

• Plan your steps and stages: Map out your stages on paper first. Identify who needs to be involved and which actions can be automated in the background.
• Create your child flows: An orchestration is a collection of individual flows. Build your screen flows and autolaunched flows first. Ensure they are designed to receive input variables from the orchestration.
• Build the orchestration: Open the Flow Builder and select New Flow, click All + Templates, and then Orchestrator. You can select either a record-triggered or autolaunched orchestration.
• Assign work to users: For interactive steps, you must decide who completes the task. You can assign work to a specific user, a group, or use a resource from the record, such as the record owner.
• Add the orchestration work guide: Navigate to the Lightning record page for the object you are automating. Drag the Orchestration Work Guide onto the page layout.

Real-world use cases for flow orchestration

Orchestration is most effective when a process involves multiple departments:

1. Complex contract approvals

A contract might be reviewed by legal, then finance, and finally signed by an executive. Orchestration manages these hand-offs. If finance rejects the budget, the orchestration can automatically route it back to the sales rep.

2. Service request fulfillment

A customer refund might involve a support agent verifying the claim, a warehouse team confirming the return, and a finance team issuing the credit. Orchestration keeps the record updated at every stage.

3. Project milestone management

For professional services teams, an orchestration can trigger the start of a “Development” stage only after the “Requirements Gathering” stage is marked as complete by the project manager.

Common challenges and solutions for flow orchestration

While orchestration is powerful, it introduces new complexities:

1. Debugging long-running processes

An orchestration could take weeks to finish, making it hard to trace variable states.

Solution: Use the Orchestration Runs list view. This provides a detailed log of every stage and step, including which ones are in progress or failed.

2. Managing permissions

Since work is assigned to different people, every user must have the correct permissions to run the underlying flows.

Solution: Regularly audit your permission sets and use sharing hierarchy to verify visibility.

Manually testing an orchestration is time-consuming.

3. Testing bottlenecks

Manually testing an orchestration is time-consuming. You often have to log in as multiple users to click through stages, and it makes regression testing difficult to do at scale, leading to a higher risk of bugs in production.

Solution: At this stage, it can be beneficial to adopt automated testing.

4. Scaling testing for complex workflows

As orchestrations grow, manual validation cannot keep up. Testing multi-user paths requires tools that understand the Salesforce architecture. Tricentis Testim for Salesforce can handle these long-running workflows.

Standard automation tools often struggle with Salesforce’s dynamic UI, but this is designed specifically for the ecosystem.

By using AI-driven creation, Tricentis analyzes your metadata to auto-generate test cases and relevant data. This eliminates hours of manual scripting. Instead of logging in as multiple users to verify a contract approval, you can automate the entire life cycle.

This confirms that every stage, decision, and background step functions correctly after every org update.

Conclusion

Salesforce flow orchestration changes how we approach automation by replacing disjointed scripts with unified business processes. By coordinating people and systems in one builder, you can manage complex hand-offs that previously required custom Apex.

However, growing complexity requires a reliable testing strategy. Tricentis’s test automation for Salesforce provides the support needed to keep your orchestrations stable as you scale.

This post was written by Chris Ebube Roland. Chris is a dedicated software engineer, technical writer, and open-source advocate. Fascinated by the world of technology development, he is committed to broadening his knowledge of programming, software engineering, and computer science. He enjoys building projects, table tennis, and sharing his expertise with the tech community through the content he creates.