You are here:
Triggered Flows
In the Start element of a triggered flow, you can specify what starts a flow. For example, the flow trigger can be a schedule or the new and changed records of a specified object. Without a trigger, you need to set up other things to launch the flow, such as custom buttons, processes, Apex classes, or even Einstein Bots.
Required Editions
| View supported editions. |
Where to Start
Choose the trigger type that matches what starts your flow, then learn to manage all your triggered flows together.
| Trigger Type | Topic | What You Learn |
|---|---|---|
| Record changes | Before-Save Record-Triggered Flows | Understand why before-save flows update records up to 10 times faster than record-change processes, which elements are available, and when to use an after-save flow instead. |
| Scheduled Paths | Add a scheduled path to a record-triggered flow so that part of the flow runs at a configurable offset after the triggering event, such as sending a follow-up message three days after a record is created. | |
| Time schedule | Schedule-Triggered Flows | Configure a flow to run once, daily, or weekly for a batch of records that meet
your filter criteria. Understand how the $Record global variable
gives each flow interview access to its record's field values. |
| External system or event | Data Cloud-Triggered Flows | Start a flow when a Data Cloud data model object (DMO) change meets your specified conditions. Learn the required permissions and how to configure the DMO trigger in the Start element. |
| Automation Event-Triggered Flows | Automatically respond to business events such as customer orders or SMS signups using provided triggers, custom Data Cloud triggers, real-time data graphs, or engagement signals you promote to the event library. | |
| On-Demand Flows | Integrate marketing flows into external systems using the standard invocable action REST endpoint. Understand the required inputs, how to grant permissions to the triggering user, and how to retrieve a flow's available inputs before calling it. | |
| Audience or segment | Audience Flows | Choose from four audience sources—segment, list, record, or campaign—to target the right group. Understand which source creates which underlying flow type and when each fits your use case. |
| Segment Flows | Send messages to everyone in a Data Cloud segment on a schedule. Learn how segment membership is managed, how exit rules work, and how to pause, resume, or deactivate a running segment flow. | |
| Managing triggers | Manage Record-Triggered Flows | Use Flow Trigger Explorer to view, filter, reorder, and navigate all record-triggered flows for a given object and trigger type, including before-save, after-save, and asynchronous paths. |
| Define the Run Order of Record-Triggered Flows for an Object | Assign a trigger order value (1–2,000) to before-save or after-save flows on the same object so they run in a predictable sequence, letting you divide automation by team or logical owner. |
IN THIS SECTION
- Schedule-Triggered Flows
A schedule-triggered flow starts at the specified time and frequency for a batch of records. Configure the schedule trigger in the Start element of your autolaunched flow. - Before-Save Record-Triggered Flows
Creating or updating a record can trigger a record-triggered flow to make additional updates to that record before it's saved to the database. A record-triggered flow can update a Salesforce record 10 times faster than a record-change process. Configure the record trigger in the Start element of your record-triggered flow. - Scheduled Paths
For record-triggered flows, you can use scheduled paths to run part of a flow at a dynamically scheduled time after a triggering event. - Audience Flows
An audience flow runs on a schedule and sends messages to a specified audience. Select a data source—segment, list, record, or campaign—when you create the flow. - Segment Flows
A segment flow sends messages to a specific group of people—called a segment—at a scheduled time. When you activate the flow, everyone in the segment receives messages at that time. - Trigger Flows with Data 360 Data
A Data Cloud-triggered flow starts when conditions are met in a data model object (DMO). - On-Demand Flows
On-demand flows are triggered by REST API calls. For example, create an automation to send your customer an SMS message that triggers after a user signs up for a membership program, or after the user clicks a button on your site. - Automation Event-Triggered Flows
Create event-triggered flows that automatically respond to business events, such as customer orders, SMS signups, or service level changes. Choose from provided triggers, define custom triggers using Data 360, real-time data graphs, or create triggers with engagement signals. - Manage Record-Triggered Flows
See, manage, reorder, and filter your record-triggered flows with Flow Trigger Explorer. Flow Trigger Explorer shows all the flows that are associated with a specified object and that run when a record is created, updated, or deleted. You can navigate between a flow in Flow Builder and other flows that run under the same circumstances. - Define the Run Order of Record-Triggered Flows for an Object
Specify a trigger order value to determine the run order of before-save or after-save flows for the same object.
Did this article solve your issue?
Let us know so we can improve!
