You are here:
Flow Approval Process Types
The type of a flow approval process determines how it's triggered and who can start it. Determine which type to use based on what starts the approval process and how much control you need over when it runs.
Required Editions
| View supported editions for Flow Approval Processes. |
All flow approval processes have steps grouped within a series of stages. Approval steps contain a screen flow and can require user interaction. Background steps contain an autolaunched flow and don't require user interaction. A flow approval process type affects how a flow approval process starts.
| Flow Approval Process Type | Available Distribution Methods | When to Use |
|---|---|---|
| Autolaunched Flow Approval Process (No Trigger) |
|
Use when users manually initiate approval requests, or when another process or external system determines when to submit for approval. Best for scenarios where a user decision or a complex condition—not just a record save—controls when the submission happens. |
| Record-Triggered Flow Approval Process | A record-triggered flow approval process runs only when a record is created or updated. | Use to start the approval automatically based on record changes, without any user action to submit. Best for automating compliance or review workflows where a record meeting certain criteria—such as a large expense report or a contract value that's more than a threshold—always requires approval. |
| External System Change-Triggered Flow Approval Process | An external system change-triggered flow approval process runs only when data changes in a supported external system. | Use when changes in a connected external system and not Salesforce record changes or user actions trigger the approval process. Requires the MuleSoft for Flow add-on. |
Choosing a Flow Approval Process Type
Before you build, consider what triggers the approval and who controls when it starts.
| If the Approval Starts When... | Use This Type |
|---|---|
| A user decides to submit | Use an Autolaunched Flow Approval Process. You add a button or link to the record page, or start the approval from Apex or a flow. Users control when to submit, and the approval doesn't run automatically. For example, a sales rep manually submits a discount request after deciding the deal needs approval. |
| A record is saved | Use a Record-Triggered Flow Approval Process. The approval runs automatically when a record is created or updated and meets the entry criteria. Users don't take any additional action to start the approval process. For example, when an opportunity's discount exceeds 20%, an approval process automatically starts to get manager sign-off. |
| Data changes in an external system | Use an External System Change-Triggered Flow Approval Process. The approval runs when a change occurs in a connected external system via MuleSoft. For example, a purchase order update in an enterprise resource planning (ERP) system triggers an approval process in Salesforce. Requires the MuleSoft for Flow add-on. |
