You are here:
Flow Types
A flow or flow version’s type determines which elements and resources you can add to a flow and how you can distribute the flow. For example, you distribute a screen flow on a website to gather information from visitors, or you distribute an autolaunched flow by using a custom button that users click to run the flow in the background. Similarly, you can add a Custom Error element only in a record-triggered flow, whereas you can add a Choice resource type only in a screen flow.
Required Editions
Standard Flow Types
These flow types are supported in Flow Builder.
| Type | Description | Available Distribution Methods | Supported in Translation Workbench? |
|---|---|---|---|
| Action Cadence Autolaunched Flow | Launches after a sales step is completed. This type of flow runs in the background without user interaction. | Sales Cloud | Yes |
| Action Cadence Step Screen Flow | Launches from a cadence step. This type of flow collects or displays information and requires user interaction. | Sales Cloud | Yes |
| Activation-Triggered Flow | Launches when an activation is published. This type of flow runs in the background without user interaction. | Data 360, Marketing Cloud Growth or Advanced with Data 360 | Yes |
| Activity-Object Matching Flow | Launches when Einstein Activity Capture detects and captures a new activity, such as an email. This type of flow runs in the background without user interaction. Requires Sync Email as Salesforce Activity to be enabled. | Sales Cloud | Yes |
| Autolaunched No Trigger Flow | Launches when invoked by a supported distribution method. This autolaunched flow runs in the background and doesn’t require user interaction. This flow type doesn’t support screens, local actions, choices, or choice sets. |
|
Yes |
| Autolaunched Flow Approval Process | Launches when invoked by Apex, REST API, custom buttons, or custom links. A flow approval process lets you create a multi-step, multi-user approval process. Includes the recordId, submitter, and submissionComments input variables. |
|
Yes |
| Autolaunched No Trigger Orchestration | Launches when invoked by Apex, REST API, custom buttons, or custom links. With an orchestration, you can create a multi-step, multi-user process. |
|
Yes |
| Automation Event-Triggered Flow | Launches when an automation event such as a form submission is received. This type of flow runs in the background without user interaction. | Data 360, Starter, or Marketing Cloud Growth
|
No |
| Broadcast Flow | Launches when referenced by Apex, REST API, or subflow element. | Data 360, Marketing Cloud Growth or Advanced with Data 360 | Yes |
| Cart Async Autolaunched Flow | Launches when invoked by a cart change, such as an add to cart. This type of flow runs in the background without user interaction. | Commerce Cloud | Yes |
| Checkout Screen Flow | Create a screen flow that implements a Commerce Cloud checkout process. This type of flow collects or displays information and requires user interaction. | Use this Experience Builder component to add this flow to your store.
|
Yes |
| CMS Workflow Orchestration Autolaunched Flow | Launches when invoked from the Workflows component in a CMS workspace. With this type of orchestration, you can create a multi-step, multi-user process to create, edit, organize, and manage digital content from a centralized location. Includes the mContentVariantId and mContentSpaceId input variables. This type of flow runs in the background without user interaction. For more details, see CMS Workflows and Approvals. | Salesforce CMS in the Digital Experiences app | Yes |
| Contact Request Screen Flow | Launches when invoked by a customer. With it, a customer can enter contact details into a self-service form. This type of flow collects or displays information and requires user interaction. | Use one of these Experience Builder components to add this flow.
|
Yes |
| Data Capture Flow | Launches when invoked by a user in the Field Service mobile app. Create, update, and pre-fill records based on data from related records in the flow. This type of flow requires user interaction. | Field Service mobile app | Yes |
| Discovery Framework Data Capture Flow | Launches when invoked by a user in the Field Service mobile app. With it, you can create forms by using the assessment questions from Discovery Framework. This type of flow collects or displays information and requires user interaction. | Field Service mobile app | Yes |
| Evaluation Autolaunched Flow | Launches when invoked by an orchestration to evaluate custom criteria for a
stage or step. To indicate that the criteria are met, set the output variable
isOrchestrationConditionMet to True, which discards all other
output variables. This type of flow runs in the background without user interaction. |
|
Yes |
| Event-Driven Flow | Launches when an event is received. This type of flow runs in the background without user interaction. Requires org and user permissions. Requires Flows: Lightning App and Flow Builder: Citizen flows org permissions and View Flows and Create or Edit Flows user permissions. | Starter, Pro Suite, or Marketing Cloud Growth
|
Yes |
| External System Change-Triggered Flow | Launches when a third-party system is polled and the results indicate that there was a change in the connected external system. | MuleSoft for Flow: Integration | Yes |
| Field Service Mobile Flow | Launches when invoked by a user in the Field Service mobile app. This type of flow collects or displays information and requires user interaction. | Field Service mobile app | Yes |
| Field Service Web Screen Flow | This flow type launches from the Field Service app. With it, users can schedule, modify, or cancel an appointment in a web browser. This type of flow requires user interaction. | Embedded Appointment Booking | Yes |
| Form-Triggered Flow | Launches when a web visitor submits a marketing form. This type of flow runs in the background without user interaction. Requires Flows: Lightning App and Flow Builder: Citizen flows org permissions and View Flows, Create or Edit Flows, and Create or Modify Form-Triggered Flows user permissions. | Marketing Cloud Growth
|
No |
| Identity User Registration Flow | Launches when a user logs in via a single sign-on (SSO) process that uses the authentication provider framework. After the third-party identity provider authenticates the user, the flow creates a user or updates an existing user. This type of flow runs in the background without user interaction. | SSO configurations that use an authentication provider | No |
| Indicator Result Screen Flow | Launches a screen flow when initiated by a user to calculate and create indicator results for a selected indicator performance period. | Outcome Management | Yes |
| Individual-Object Linking Screen Flow | Launches when invoked by an agent to link a record like a case or messaging session to a contact, lead, person account, or employee. This type of flow collects or displays information and requires user interaction. | Service Cloud | Yes |
| Loyalty Management Autolaunched Flow | Launches when invoked by a loyalty program process, and contains Assignment, Decision, and Action elements. The Action element in this type of flow supports Apex and quick actions. This type of flow runs in the background without user interaction. | Loyalty Management app | Yes |
| Mortgage Lending Screen Flow | Launches when invoked by a user and allows them to provide Financial Service Cloud mortgage application details. This type of flow requires user interaction. | Financial Service Cloud | Yes |
| Platform Event Triggered Flow | Launches when a platform event occurs. This type of flow runs in the background without user interaction. | Platform Events in Setup | Yes |
| Prompt Template Capability-Triggered Flow | Launches from a prompt template. Adds prompt instructions to the associated prompt template. This type of flow adds content to the associated prompt template and runs in the background without user interaction. | Prompt Builder | Yes |
| On-Demand Flow | Launches when referenced by the REST API. This autolaunched flow runs asynchronously in the background. | Data 360, Marketing Cloud Next Growth and Advanced editions. | Yes |
| Recommendation Strategy Autolaunched Flow | Builds a personalized list of recommendations for users. When a user responds to a recommendation, that recommendation launches its assigned flow. Used by Einstein Next Best Action. |
|
Yes |
| Record-Triggered After Save Flow | Launches and runs in the background after a record change is saved or a record is deleted. | A record-triggered after save flow runs only when a record is saved, can make changes only to records related to the triggering record, and runs in the background without user interaction. | Yes |
| Record-Triggered After Save Flow Approval Process | Launches when a record is created or updated. A flow approval process lets you create a multi-step, multi-user approval process. | A record-triggered after save flow approval process runs only when a record is created or updated. | Yes |
| Record-Triggered After Save Orchestration | Launches when a record is created or updated. With an orchestration, you can create a multi-step, multi-user process. This type of flow runs in the background without user interaction. See Orchestration Types for Flow Orchestration availability. | A record-triggered after save orchestration runs only when a record is created or updated. | Yes |
| Record-Triggered Before Delete Flow | Launches when a record is deleted. This type of flow runs in the background without user interaction. | A record-triggered before delete flow runs when a record is flagged for deletion and runs in the background without user interaction. | Yes |
| Record-Triggered Before Save Flow | Launches after a record is created or updated, but hasn't been saved. Only these elements are supported: Assignment, Decision, Get Records, and Loop. | A record-triggered before save flow runs only when a record is created or updated, can make changes only to the triggering record, and runs in the background without user interaction. | Yes |
| Schedule-Triggered Flow | Launches and runs in the background at a specified time and frequency for each record in a batch. This flow type doesn’t support user interaction, screens, local actions, choices, or choice sets. | A schedule-triggered flow runs only at the scheduled time and frequency. | Yes |
| Screen Flow | Guides users through a business process that is launched from a supported distribution method. This flow type requires user interaction because it includes screens, local actions, steps, choices, or dynamic choices. Screen flows don’t support Wait elements. |
|
Yes |
| Segment-Triggered Flow | Launches when activated or when scheduled for qualified Data 360 segment members. This type of flow runs in the background without user interaction. Requires org and user permissions. Requires Flows: Lightning App and Flow Builder: Citizen flows org permissions and View Flows, Create or Edit Flows, and Create or Modify Segment-Triggered Flows user permissions. | Data 360, Starter, Pro Suite, or Marketing Cloud Growth
|
No |
| User Provisioning Screen Flow | Launches when invoked by a user. With it, users can create a user account and link it to a third-party service or app. This type of flow requires user interaction. For example, use this flow type to customize the user provisioning configuration for a connected app to link Salesforce users with their Google Apps accounts. |
A user provisioning flow can only be implemented by associating it with a connected app when running the User Provisioning Wizard. | No |
Other Flow Types
Not all flow types are supported in Flow Builder. Some flow types are used only in other parts of Salesforce, so they’re not listed in the Flows page in Setup. However, the list of paused flow interviews can include these types.
| Type | Description | Supported in Translation Workbench? |
|---|---|---|
| Customer Lifecycle Record-Triggered After Save Flow | Launches after a customer lifecycle map is saved. This flow type changes records related to the triggering record. This type of flow runs in the background without user interaction. | Yes |
| Data Cloud Data Change Flow | Launches when a record from a Data 360 data model object or a calculated insight object is changed and meets the specified conditions. This type of flow runs in the background without user interaction. | Yes |
| Digital Form Screen Flow | Launches from app extensions. This type of flow collects or displays information and requires user interaction. | Yes |
| Employee Service Catalog Item Screen Flow | Launches when invoked by a user. With it, users can browse and order items from the Employee Service Catalog. This type of flow collects or displays information and requires user interaction. | No |
| Process Builder Autolaunched Process | Launched when invoked from a Process Builder process. This type of flow runs in the background without user interaction. | No |
| Process Builder Custom Event Process | A Process Builder process that launches when a custom event message is received. This type of process runs in the background without user interaction. | No |
| Process Builder Workflow | Launches when a record is created or updated. This type of process runs in the background without user interaction. | No |
| Survey Enrich Autolaunched Flow | Launches in the context of a survey response and can’t execute without a corresponding survey. Use it to conditionally map a response to a record, create records, or send notifications. This type of flow runs in the background without user interaction. | No |
| Transaction Security Autolaunched Flow | Used by Condition Builder to declaratively build customized security policies to protect data. This type of flow runs in the background without user interaction. | No |
| Managed Content Autolaunched Flow | Launches when invoked by the ManagedContentRelease translator. This type of flow runs in the background without user interaction. | Yes |
| Routing Autolaunched Flow | Launches when a customer initiates a chat, voice, or messaging conversation and routes the work item to a queue, skill, agent, or bot. This type of flow runs in the background without user interaction. | No |
| Scheduler Appointments Screen Flow | Launches when invoked by a user. With it, users can schedule appointments in Salesforce Scheduler. This type of flow collects or displays information and requires user interaction. | Yes |
Did this article solve your issue?
Let us know so we can improve!
