Autolaunched Flow
An Autolaunched Flow is a Salesforce Flow that runs without showing any screens to a user.
Definition
An Autolaunched Flow is a Salesforce Flow that runs without showing any screens to a user. It executes server-side in response to a trigger: a record save (Record-Triggered Flow), a Platform Event (Platform Event-Triggered Flow), a scheduled time (Scheduled-Triggered Flow), an Apex call (Flow.Interview.start), a Process Builder, another Flow (subflow), or an external system through the Flow REST API. Autolaunched Flows are the workhorse automation pattern in modern Salesforce; they replaced most Workflow Rules, Process Builders, and many Apex triggers from the 2020 era forward.
Autolaunched Flows differ from Screen Flows in one key respect: no screens. Logic, data manipulation, decision branches, loops, callouts, and DML all work the same way; the difference is who sees the result. A Screen Flow renders an interactive wizard to the running user. An Autolaunched Flow runs invisibly, returning control to the caller only when finished. This makes Autolaunched Flows the right tool for background automation, integrations, and any workflow that fires from a non-user event. They share most of the Flow Builder canvas, the same debug tools, and the same governor limits as other Flow types.
How Autolaunched Flows fit Salesforce automation
The trigger types
Record-Triggered (fires before save or after save on insert, update, delete), Scheduled-Triggered (fires on cron schedule), Platform Event-Triggered (fires when a platform event publishes), and plain Autolaunched (fires via explicit invocation from Apex, Process Builder, REST, or another Flow). The trigger type decides what the Flow is invoked from.
Record-Triggered Flows replace most legacy automation
Salesforce officially recommends Record-Triggered Flows over Workflow Rules and Process Builder for new automation. Workflow Rules are retired. Process Builder is in maintenance mode. Record-Triggered Flows handle the same use cases (field updates, email alerts, related record creation) plus much more (loops, complex conditions, callouts) in one engine.
Before Save versus After Save context
Record-Triggered Flows can run Before Save (modify the same record without DML, very fast) or After Save (after the record commits, can interact with related records, slower). Before Save is the modern replacement for Workflow Rule field updates; After Save handles broader automation needs.
Scheduled-Triggered Flows
Scheduled-Triggered Flows replace many uses of Scheduled Apex. The Flow defines a cron schedule plus an optional record set query, and the Flow runs at the scheduled time once per matching record. Useful for daily renewal reminders, stale-record cleanup, and cadence-driven outreach.
Platform Event-Triggered Flows
When a Platform Event publishes, a subscribed Flow fires once per event message. This is the supported pattern for reacting to external system messages (a payment processor sends an event when a charge succeeds). Platform Event-Triggered Flows run async with their own governor limits.
Calling Apex and being called from Apex
Autolaunched Flows can call Apex through invocable methods and Apex Actions. Apex can call Flows through Flow.Interview.start. The bidirectional callability lets developers and admins collaborate; Flow handles the orchestration, Apex handles the heavy lifting where Flow falls short.
Governor limits and bulkification
Autolaunched Flows respect the same governor limits as the triggering transaction. Record-Triggered Flows process multiple records in one transaction; the Flow must be bulkified to handle the full batch. Loops with DML inside can blow limits the same way unbulkified Apex would. Flow Builder tooling helps, but discipline still matters.
Debugging and monitoring
Flow Builder includes a Debug feature that runs the Flow with sample inputs and shows the step-by-step execution. Failed flows surface on the Failed Flow Interviews list. Apex Exception Email covers Flow errors. Production teams build dashboards on FlowInterview history for fail-rate and average elapsed-time tracking.
How to build an Autolaunched Flow
Autolaunched Flows replace most legacy declarative automation. Building one well takes the same care as Apex: trigger choice, bulkification, error handling, and debug.
- Pick the trigger type
Record-Triggered for record changes. Scheduled-Triggered for cron. Platform Event-Triggered for async event responses. Plain Autolaunched for explicit invocation from Apex, Process Builder, or REST.
- Design the flow in Flow Builder
Drag elements (Get Records, Update Records, Decision, Loop, Apex Action) onto the canvas. Keep the canvas readable; complex Flows benefit from sub-flows.
- Bulkify loops carefully
Collect records in a variable, perform a single bulk DML at the end. Loops with DML inside fail at scale; bulkification is mandatory.
- Add fault paths and error handling
Drag fault connectors out of DML and Apex Action elements. Route failures to a fault path that logs the error to a custom object for later review.
- Debug, test, and activate
Use Flow Debug with realistic data. Once the run passes, save as Active. Test in a sandbox at scale before activating in production.
Record-Triggered, Scheduled, Platform Event, or plain Autolaunched.
The object whose changes fire the Flow.
Before Save or After Save for Record-Triggered Flows.
Cron-style timing and optional record-set query.
Error-handling routes attached to DML and Apex Action elements.
- Loops with DML inside fail at scale. Collect records first, DML once at the end; bulkification is mandatory.
- Before Save Flows cannot do DML on other records. Use After Save when the Flow needs to touch related records.
- Scheduled-Triggered Flows run once per matching record at the scheduled time. Large record sets can exceed daily Flow execution limits.
- Recursion can occur if a Flow updates a record that re-triggers the same Flow. Add a recursion guard or design the trigger condition to exclude self-updates.
Trust & references
Cross-checked against the following references.
- Autolaunched FlowsSalesforce Help
- Flow OverviewSalesforce Help
Straight from the source - Salesforce's reference material on Autolaunched Flow.
- Flow BuilderSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What distinguishes an Autolaunched Flow from a Screen Flow?
Q2. Which of these can trigger an Autolaunched Flow?
Q3. What are Autolaunched Flows the modern replacement for?
Discussion
Loading discussion…