Flow Types in Salesforce are different categories of automated processes that allow administrators to build powerful business automation solutions. Each flow type serves a specific purpose and triggers under different conditions.
**Screen Flows** are interactive flows that guide users through a se…Flow Types in Salesforce are different categories of automated processes that allow administrators to build powerful business automation solutions. Each flow type serves a specific purpose and triggers under different conditions.
**Screen Flows** are interactive flows that guide users through a series of screens to collect and display information. Users manually launch these flows from buttons, links, Lightning pages, or Experience Cloud sites. They are ideal for guided processes like case creation or lead qualification.
**Record-Triggered Flows** execute when a record is created, updated, or deleted. These replace Process Builder and Workflow Rules as the preferred automation tool. They run in the background and can perform actions before or after the record is saved to the database. Use cases include field updates, creating related records, or sending notifications.
**Schedule-Triggered Flows** run at specified times and frequencies, such as daily, weekly, or monthly. They process batches of records that meet defined criteria. Common applications include sending reminder emails, updating record statuses, or performing routine data maintenance.
**Platform Event-Triggered Flows** respond to platform event messages, enabling real-time integration scenarios. They execute when the system receives a specific platform event.
**Autolaunched Flows** run in the background and can be called from other automation tools, Apex code, or REST API. They contain no screen elements and execute entirely behind the scenes.
**Subflows** are reusable flow components that can be called from other flows, promoting modular design and reducing redundancy.
Understanding these flow types helps administrators select the appropriate automation approach for each business requirement. Salesforce recommends using flows as the primary automation tool, as they offer the most flexibility and will continue receiving platform enhancements. The Flow Builder provides a visual interface for creating all flow types, making automation accessible to administrators at various skill levels.
Flow Types in Salesforce: A Comprehensive Guide
Why Flow Types Matter
Understanding Flow Types is essential for Salesforce Administrators because flows are the primary automation tool in Salesforce. Different flow types serve different purposes, and selecting the correct type determines how and when your automation runs. On the Salesforce Administrator exam, you can expect multiple questions testing your knowledge of when to use each flow type.
What Are Flow Types?
Flow Types are categories of automation in Salesforce Flow Builder that define how a flow is triggered and executed. Each type has specific use cases and behaviors. Salesforce currently offers several main flow types:
1. Screen Flow Screen Flows provide a user interface and require user interaction. They guide users through a series of screens to collect information or display data. These are launched by users clicking buttons, links, or accessing them through tabs and Lightning pages.
2. Record-Triggered Flow These flows run automatically when a record is created, updated, or deleted. They replace Process Builder and Workflow Rules as the recommended automation tool. Record-Triggered Flows can run before or after the record is saved to the database.
3. Schedule-Triggered Flow Schedule-Triggered Flows run at specified times and frequencies. They can process batches of records that meet defined criteria, making them ideal for recurring maintenance tasks or time-based operations.
4. Platform Event-Triggered Flow These flows execute when a platform event message is received. They are used for event-driven architectures and real-time integrations.
5. Autolaunched Flow (No Trigger) Autolaunched Flows run in the background and can be called from other automations, Apex code, or REST API. They do not have screens and cannot be started by users clicking a button.
How Flow Types Work
Screen Flows present interactive screens to users. They can include input fields, display text, choices, and data tables. When a user completes the flow, data can be created, updated, or deleted based on the flow logic.
Record-Triggered Flows evaluate entry conditions when the specified DML operation occurs. They can be configured to run: - Before Save: Runs before the record is committed, allowing field updates on the triggering record using fast field updates - After Save: Runs after the record is committed, allowing related record operations and actions that require a record ID
Schedule-Triggered Flows run at the defined schedule and query records matching the specified criteria. They process records in batches and are subject to governor limits.
Platform Event-Triggered Flows subscribe to a platform event and execute each time an event message is published.
Autolaunched Flows require an external trigger such as another flow, a process, Apex, or an API call to execute.
Exam Tips: Answering Questions on Flow Types
Tip 1: Identify the Trigger When a question describes a scenario, first identify what initiates the automation. User action suggests Screen Flow. Record changes suggest Record-Triggered Flow. Time-based requirements suggest Schedule-Triggered Flow.
Tip 2: Consider User Interaction If the scenario requires displaying information to users or collecting input, Screen Flow is the answer. If automation should run in the background with no user interface, consider Record-Triggered or Autolaunched Flows.
Tip 3: Before vs After Save Questions often test whether you understand the difference. Use Before Save when updating fields on the same record that triggered the flow. Use After Save when creating or updating related records, sending emails, or performing operations that need the record ID.
Tip 4: Batch Processing If a scenario involves processing multiple records on a schedule or performing cleanup tasks, Schedule-Triggered Flow is typically correct.
Tip 5: Watch for Keywords Look for keywords like automatically (Record-Triggered), wizard or guided (Screen Flow), nightly or weekly (Schedule-Triggered), and real-time integration (Platform Event-Triggered).
Tip 6: Eliminate Wrong Answers Know what each flow type cannot do. Screen Flows cannot run in the background. Record-Triggered Flows cannot display screens. Schedule-Triggered Flows cannot respond to record changes in real-time.
Tip 7: Remember the Retirement of Process Builder Salesforce recommends Record-Triggered Flows over Process Builder and Workflow Rules. Exam questions will likely point toward flows as the preferred solution.