Answer
Record-Triggered Flows in Salesforce are automatic flows that run in response to data changes on records. You trigger a Record-Triggered Flow by configuring the flow to listen to specific object events and entry conditions. When the configured event occurs (create, update, or delete) and the entry criteria are satisfied, Salesforce launches the flow in the chosen execution context.
Key trigger options
When you configure a Record-Triggered Flow, you choose three primary trigger settings:
1) Object event (when to run)
Set which data change should start the flow:
Created — runs only when a record is created.
Updated — runs only when a record is updated.
Created or Updated — runs for both create and update operations.
Deleted — runs when a record is deleted (supported for after-save flows).
2) Run the Flow (before-save vs after-save vs scheduled)
Choose the execution timing:
Before-Save (Fast Field Updates) — executes prior to the record being committed. Use this to make quick field changes without extra DML. Best for validation-normalization and setting system fields.
After-Save — executes after the record has been saved. Use this when you need the record ID, want to kick off related record changes, call Apex, or perform callouts (with asynchronous patterns).
Scheduled Actions (Post-commit) — in some flows you can schedule actions to run at a defined time after the triggering event.
3) Entry Conditions & Condition Requirements
Define which records should trigger the flow using entry criteria. You can require either:
All Conditions Are Met (AND) or Any Condition Is Met (OR). Optionally, select “Run the flow only when a record is updated to meet the condition” to avoid repeated runs when unchanged fields trigger updates.
Example configuration
Here’s a simple configuration example for a flow that sets a field when an Opportunity becomes Closed Won:
Object: Opportunity
Trigger: Created or Updated
Run the Flow: After-Save
Entry Condition: StageName = 'Closed Won'
Condition Requirement: All Conditions Are Met
Important behavior and best practices
– Use before-save flows for performance: Before-save flows are faster and consume fewer resources because they don’t perform an extra DML operation. Use them for field updates on the triggering record only.
– Avoid recursion: When an after-save flow updates the same record, it can cause another update event. Use entry criteria carefully and the option “Only when a record is updated to meet the condition” or use a flag field to prevent recursion.
– Bulkification: Flows process batches of records. Use collection-aware elements and avoid element designs that assume a single-record context.
– Use the right execution context: If you need the record ID, related record queries, or to create related records, use after-save. Use before-save for quick field set operations.
Flow vs Apex triggers
Record-Triggered Flows can replace many common use cases for Apex triggers (simple field updates, related record creation, routing). However, for complex business logic, heavy integrations, or where unit-testable Apex is required, consider Apex triggers or Apex classes. Always weigh maintainability and governor limits.
Troubleshooting tips
– Use the Flow Debugger with a sample record to step through the flow logic.
– Enable debug logs for the running user to inspect flow failures.
– Monitor the Flow Errors list (Setup > Paused and Failed Flow Interviews) for exceptions.
Quick checklist to trigger a Record-Triggered Flow
1. Select the Object to monitor.
2. Choose the Trigger event (Create / Update / Delete / Created or Updated).
3. Pick execution timing (Before-Save / After-Save / Scheduled).
4. Define Entry Conditions and Condition Requirements.
5. Save and Activate the Flow.
Follow these steps and your Record-Triggered Flow will run automatically when matching record events occur, enabling powerful no-code automation inside Salesforce.