Definition
A Flow Trigger is the event configuration that determines when and why a flow executes. In Record-Triggered Flows, the trigger specifies the object being monitored and the DML event (record creation, update, or deletion) that causes the flow to run. The trigger also defines whether the flow runs before or after the record is saved, and can include entry conditions that further filter which records activate the flow. It is the initiating condition of the flow, not the actions the flow performs.
Real-World Example
the Salesforce admin at FreshStart Inc. recently implemented Flow Trigger to automate a multi-step process that previously required three different people to complete manually. Flow Trigger now handles the entire sequence in seconds, sending notifications at each step and logging every action for audit purposes.
Why Flow Trigger Matters
A Flow Trigger is the event configuration that determines when and why a flow executes. In Record-Triggered Flows, the trigger specifies the object being monitored (like Account or custom object), the DML event (record creation, update, or deletion) that causes the flow to run, whether the flow runs before or after the record is saved, and optional entry conditions that further filter which records activate the flow. The trigger is the initiating condition, not the actions the flow performs.
Flow triggers are the modern replacement for Workflow Rule trigger criteria and Process Builder triggers. The before-save versus after-save distinction is important: before-save triggers can modify the record being saved without needing a separate update, making them more efficient for field updates that would otherwise require a second DML operation. After-save triggers run after the record is committed and can do things before-save can't, like making callouts or updating related records. Choosing the right trigger type affects both performance and capability.
How Organizations Use Flow Trigger
- •BrightEdge Solutions — Uses before-save triggers for field updates on the same record being saved, avoiding the extra DML overhead of after-save updates.
- •NovaScale — Uses after-save triggers when flows need to update related records, make callouts, or do other work that can't happen in before-save.
- •Cobalt Ventures — Uses entry conditions on triggers to filter which records activate the flow, reducing unnecessary flow executions on records that don't need processing.