Record-Triggered Orchestration Flow in Salesforce (Complete Guide)

In Salesforce, automation plays a very important role in reducing manual work and improving business efficiency.

One of the most powerful automation tools available today is Flow. Among different types of flows, Record-Triggered Flow is widely used because it automatically runs when a record is created, updated, or deleted.

Now, Salesforce has introduced an advanced concept called Record-Triggered Orchestration Flow, which helps manage complex business processes involving multiple steps, users, and stages.

The flows are the most powerful automation tool provided by Salesforce. They can be used to perform various tasks, such as field updates, sending emails, sending custom notifications, and more.

In this Salesforce tutorial, we will learn about Create Record Triggered Orchestration Flow in Salesforce. In this article, we will see the record trigger orchestration flow and when we can use it.

Additionally, we will see how to create a record-triggered orchestration flow in Salesforce, with real-time scenarios and step-by-step explanations.

Table of Contents

What is Record-Triggered Flow?

A Record-Triggered Flow is an automation that runs automatically when a record changes in Salesforce. It follows a simple logic:

“If something happens → then perform some action.”

For example:

When an Account is created → create a Task
When Opportunity is closed → send email

These flows run in the background without user interaction.

What is Orchestration Flow in Salesforce?

Orchestration Flow is used when your business process is:

Multi-step
Multi-user
Requires approvals or stages

Instead of handling everything in a single flow, orchestration helps you:

Break the process into stages
Assign tasks to different users
Control execution flow

What is Record-Triggered Orchestration Flow in Salesforce?

Record-Triggered Orchestration Flow is a combination of:

Record-triggered automation
Multi-step orchestration process

It starts automatically when a record is created or updated and then executes a sequence of stages and steps.

In simple words: “When a record changes → start a multi-step business process.”

Record Trigger Orchestration Flow launches when a record is created or updated. An orchestration lets you create a multi-step, multi-user process. Usually, we use an Apex trigger to accomplish this, but now we can also use a flow.

Orchestration is a sequence of stages with multiple actions and elements, and therefore, Record-Trigger Orchestration is a flow that executes when a record is created or updated, based on which stages are executed.

Let’s take an example: the relationship manager will be present when you open an account in the bank. Once the account is opened, you need to deposit some amount into it, which the cashier will do.

Then again, as the cashier enters the deposit amount, the transaction record should be created in the transaction object.

This whole process can be automated with the help of Record Trigger Orchestration Flow by putting different stages and by putting elements into those different stages

Create Record-Triggered Orchestration Flow in Salesforce

Using the above example and the following steps, we can create a record trigger orchestration flow in Salesforce.

Prerequisites:

1. We need to create two custom objects named Bank Account_c and Transactions_c.

Bank Account: It will hold information about bank account holders.
Transactions: It will hold the information on transactions that the bank’s holders have made.

Create Record Trigger Orchestration Flow

2. Log in to the Salesforce Org. -> Click on the Setup. -> Home Tab. -> Search for Flows. You will see an option under Process Automation. -> Click on Flows.

Click on the New Flow button to create a new flow.

Here, we are using Record Trigger Orchestration Flow. Select it and click the Create button.

3. In our scenario, the flow should trigger when the user creates a new bank account. That’s why I have selected the User in the Object field. In Configure Trigger, I have selected “A Record is Created” because the flow should trigger when we update the record.

According to our scenario, we will not have any conditions right now, so we don’t need to Set Entry Conditions.

Create Record Triggered Orchestration Flow in Salesforce

4. Now, we will add some elements to the flow. For that, click on the + Add Element icon. Here, you will see that there are only two kinds of elements: Stage and Decision.

As you select Stage Element and click on the Add Step option, you will see the following two kinds of steps:

Background Step: Any operations that can be done in the background, such as creating or updating records or sending an email, are background operations.
Interactive Step: Whenever we add a screen to the user’s UI, that is the interactive step.

5. Before moving ahead, as per our scenario, whenever the bank account is created, the information should be transferred to the cashier.

Here, the cashier should be able to see a specific screen where they can enter the required information, and a transaction record should be created for the account.

To create a screen, we need to create a Screen Component that defines fields such as Amount (Currency Field) and Date/Time. That information will be put in by the cashier. Here I have already created a screen component with the following fields.

Record Triggered Orchestration Flow in Salesforce

Now, we need to create a new resource to store the Bank Account ID. In the resource type, select Variable, enter the API Name, and select Data Type as Text.
We will use the API Name as the value for the next element and mark this resource as Available for Input.
Once the cashier provides that information, we need to create a transaction record by clicking on the Create Records element.

In the Object field, select the object record we are creating. Here, we are creating a record for the Transaction_c object.

Then, in the Field option, select the transaction field, and in the Value field, select the screen element value from the screen component.

Field (Transaction Object)	Value
Enter Amount	Amount (From Screen Component).
Account_c	bankAccountId (From Variable Resource).

The Account_c field is the Lookup field that describes the relation between the Bank Account and the Transaction object.

Record Triggered Orchestration Flow in Salesforce example

I have saved the flow named Cashier Screen Flow and activated it. We will apply this flow in the Record Trigger Orchestration Flow.

6. Then, to automate the process, we need to add stages to the flow. For that, click the Stage Element, and before selecting the step, enter the Label for the stage. Here, I have entered the Account Opening Stage. API Name will automatically populate.

Then, we need to select When to Complete the Step. Here, we will select this Condition-> whenever all steps have been marked Complete. The stage mark is complete.

Create the Record Triggered Orchestration Flow in Salesforce

7. Now, we need to add a step to the Stages Element so that, as per the scenario, when the account is created, the items should be transferred to the cashier. The cashier can enter the necessary details, and a transaction record will be created.

For that, we need to add an Interactive Step. Enter the Label for the step. API Name will automatically populate. Then apply the following Condition: When the stage starts, the step starts.

Then, in the Action to Run, select the Screen Flow we created for the cashier. Here, I have selected Cashier Screen Flow. When selecting the screen flow, we need to specify input values. Here, we need to select $Record > Bank Account_c > Record ID.

How to Create Record Triggered Orchestration Flow in Salesforce

Now, we need to select the Assignee Type. I have selected User, which means this screen will be visible to the user we will select in the next option. Here, select a User with a Salesforce License.

Then select where we want this interactive screen to happen. Here, I have selected Bank Account Record.

When the screen flow is complete, this step is also marked as complete.

Creates Record Triggered Orchestration Flow in Salesforce

8. After setting up all labels and conditions, click the Save button to save the flow. For that, we need to enter the Flow Label. The API Name will automatically populate as we click the text box. The Description is optional; we can introduce our flow shortly.

After saving the flow, click on the Debug button. Then click on the Activate button; always remember to debug the flow before activating it. It’s good practice to use flow.

This is how we can Record Triggered Orchestration Flow in Salesforce.

Before-Save vs After-Save Flow in Salesforce

Feature	Before-Save Flow	After-Save Flow
Execution Time	Before record saved	After record saved
Speed	Faster	Slower
Use Case	Field update	Complex logic
Related Records	No	Yes

Before-save flows are faster and used for simple updates, while after-save flows handle complex actions.

Flow vs Apex Trigger in Salesforce

Feature	Flow	Apex Trigger
Coding Required	No	Yes
Complexity Handling	Medium	High
Maintenance	Easy	Difficult
Performance	Good	High

Conclusion

Record-Triggered Orchestration Flow is a powerful feature in Salesforce that automates complex business processes across multiple stages and users. It combines the simplicity of flows with the power of structured orchestration, making large-scale automation easier to manage.

By using proper design, real-time use cases, and best practices, you can build scalable and efficient automation solutions without writing code.