Auto-launched Flows are a powerful automation tool in Salesforce that run in the background without any user interaction or screen elements. Unlike Screen Flows that require user input through visual interfaces, Auto-launched Flows execute automatically when triggered by specific events or processe…Auto-launched Flows are a powerful automation tool in Salesforce that run in the background without any user interaction or screen elements. Unlike Screen Flows that require user input through visual interfaces, Auto-launched Flows execute automatically when triggered by specific events or processes within the Salesforce platform.
These flows can be invoked through several methods including Process Builder, Apex code, REST API, or as record-triggered flows. When configured as record-triggered, they can execute before or after a record is saved, giving administrators flexibility in when the automation runs relative to database operations.
Auto-launched Flows are particularly valuable for complex business logic that needs to happen behind the scenes. Common use cases include updating related records, creating multiple records across different objects, performing calculations, sending outbound messages, and executing conditional logic based on field values.
Key characteristics of Auto-launched Flows include their ability to run in system context or user context, depending on configuration. System context means the flow runs with full system permissions, while user context respects the running user's permissions and sharing rules. This distinction is important for security and data access considerations.
Administrators can build Auto-launched Flows using Flow Builder, Salesforce's declarative automation tool. The builder provides a visual interface for creating flow elements such as assignments, decisions, loops, record operations, and subflow calls. Variables can store and manipulate data throughout the flow execution.
Best practices for Auto-launched Flows include bulkifying operations to handle multiple records efficiently, implementing proper error handling, and testing thoroughly in sandbox environments before deployment. Administrators should also consider governor limits when designing complex flows.
Auto-launched Flows represent Salesforce's strategic direction for automation, as they are part of the Flow framework that is gradually replacing older tools like Workflow Rules and Process Builder.
Auto-launched Flows: Complete Guide for Salesforce Administrators
What are Auto-launched Flows?
Auto-launched Flows are a type of Salesforce Flow that run in the background and do not require user interaction. Unlike Screen Flows, which present users with visual interfaces, Auto-launched Flows execute automatically when triggered by specific events, processes, or other automation tools.
Why are Auto-launched Flows Important?
Auto-launched Flows are critical for Salesforce Administrators because they:
• Enable complex business logic automation that runs behind the scenes • Can be triggered by record changes, scheduled times, or platform events • Replace legacy automation tools like Process Builder and Workflow Rules • Support both before-save and after-save record operations • Allow integration with external systems through Apex actions and HTTP callouts • Provide a scalable, maintainable automation solution
How Auto-launched Flows Work
Auto-launched Flows can be triggered in several ways:
1. Record-Triggered Flows: These run when a record is created, updated, or deleted. They can execute before the record is saved (Before Save) or after the record is saved (After Save).
2. Schedule-Triggered Flows: These run at specified times, either once or on a recurring schedule, processing batches of records that meet defined criteria.
3. Platform Event-Triggered Flows: These respond to platform events published by Salesforce or external systems.
4. Called by Other Automation: Auto-launched Flows can be invoked by Apex code, other flows, or REST API calls.
Before-Save vs. After-Save Flows
Before-Save Flows: • Run before the record is committed to the database • Cannot create or update related records • More efficient for field updates on the triggering record • Use $Record to reference and modify the triggering record
After-Save Flows: • Run after the record is saved to the database • Can create, update, or delete related records • Required when you need the record ID for related operations • Can send emails, post to Chatter, and perform callouts
Key Features and Capabilities
• Entry Conditions: Define which records trigger the flow based on field values • Scheduled Paths: Execute additional actions after a time delay • Fault Handling: Manage errors gracefully with fault connectors • Bulkification: Flows are automatically bulkified to handle multiple records efficiently
Exam Tips: Answering Questions on Auto-launched Flows
Tip 1: Know the Trigger Types Understand when to use Record-Triggered, Schedule-Triggered, and Platform Event-Triggered flows. Questions often ask which trigger type is appropriate for a given scenario.
Tip 2: Before-Save vs. After-Save Decisions Remember that Before-Save flows are best for updating fields on the same record, while After-Save flows are necessary for creating or updating related records.
Tip 3: Understand Limitations Auto-launched Flows cannot display screens to users. If a question mentions user input or visual elements, Auto-launched Flow is not the correct answer.
Tip 4: Order of Execution Know where Auto-launched Flows fit in Salesforce's order of execution. Before-Save flows run before validation rules, while After-Save flows run after record commit.
Tip 5: Scheduled Paths When questions mention actions that should occur hours or days after a record change, think of Scheduled Paths in Record-Triggered Flows.
Tip 6: Migration from Legacy Tools Salesforce recommends migrating Workflow Rules and Process Builder to Flow. Expect questions about which Flow type replaces specific legacy automation.
Tip 7: Transaction Boundaries Auto-launched Flows share the same transaction as the triggering event. This means governor limits are shared, and a flow error can roll back the entire transaction.
Tip 8: Read Scenarios Carefully Pay attention to keywords like automatically, in the background, or no user interaction – these indicate Auto-launched Flows are appropriate.