Record-Triggered Flows in Salesforce automate processes when records are created, updated, or deleted. There are two main types based on timing: Before-Save and After-Save flows.
Before-Save Flows run early in the save process, before the record is committed to the database. Because the record is …Record-Triggered Flows in Salesforce automate processes when records are created, updated, or deleted. There are two main types based on timing: Before-Save and After-Save flows.
Before-Save Flows run early in the save process, before the record is committed to the database. Because the record is still in memory, you can update field values on the triggering record itself using simple assignments, and these changes are saved as part of the same transaction. This makes Before-Save flows extremely fast and efficient, often up to ten times faster than other automation. However, they have limitations: you cannot create or update related records, send emails, call subflows, or perform actions on other objects. Use Before-Save flows when your goal is only to update the same record that triggered the flow.
After-Save Flows run after the record has been committed to the database. At this point, the record has an ID and is fully saved. This allows you to perform a wide range of actions, such as creating or updating related records, sending emails, launching subflows, calling Apex actions, and posting to Chatter. Because these flows operate after the save, they are more powerful but also more resource-intensive compared to Before-Save flows. To update the same triggering record in an After-Save flow, an additional update operation is required, which consumes more system resources.
Choosing between the two depends on your requirement. If you only need to modify fields on the same record, choose Before-Save for better performance. If you need to interact with related records or perform broader actions, choose After-Save. Understanding this distinction helps administrators build efficient, scalable automation while respecting governor limits. Both types share the same trigger conditions, allowing you to specify when the flow should run based on record changes and entry criteria.
Before-Save vs After-Save Record-Triggered Flows
Why This Topic Matters Understanding the difference between Before-Save and After-Save Record-Triggered Flows is essential for any Salesforce Administrator. Choosing the correct flow type affects performance, governor limit consumption, and whether your automation works as intended. Exam questions frequently test your ability to select the right trigger timing for a given scenario.
What Are Record-Triggered Flows? A Record-Triggered Flow runs automatically when a record is created, updated, or deleted. Salesforce lets you decide when the flow runs relative to the database save operation. This is where the two options come in:
1. Before-Save (Fast Field Updates) — Runs before the record is committed to the database. 2. After-Save (Actions and Related Records) — Runs after the record has been saved to the database.
How Before-Save Flows Work Before-Save flows execute during the initial save, prior to the data being written to the database. Because the record is still in memory, you can update field values on the triggering record itself with no extra DML operation required.
Key characteristics: • Extremely fast (up to 10x faster than other automation for field updates). • Can only update the record that triggered the flow. • Cannot create records, send emails, or call other actions. • Cannot access the flow's full action library. • No additional DML is used, so they help conserve governor limits.
How After-Save Flows Work After-Save flows execute once the triggering record is already saved. At this point the record has an Id and is fully committed, which means you can perform a wider range of operations.
Key characteristics: • Can create, update, or delete related records. • Can send emails, post to Chatter, and call subflows or Apex. • Can access the full set of flow actions. • Uses additional DML when updating the triggering record. • Slightly slower because it happens as a separate operation after the save.
Choosing the Right Type Use Before-Save when you only need to set or change field values on the same record that fired the flow. Use After-Save when you need to work with related records, send notifications, or call other actions.
Quick Comparison • Update same record's fields: Before-Save is best. • Create or update related records: choose After-Save. • Send an email or post to Chatter: choose After-Save. • Fastest field update with fewest resources: Before-Save. • Need the record Id for the triggering record: After-Save (the Id exists after the save).
Exam Tips: Answering Questions on Before-Save vs After-Save Record-Triggered Flows • When a question mentions updating fields on the same record and emphasizes speed or efficiency, the answer is almost always Before-Save. • When a scenario requires creating related records, sending emails, or posting to Chatter, select After-Save. • Remember that Before-Save flows conserve governor limits since they use no extra DML for updating the triggering record. • Watch for keywords like performance, fast field update, or same record — these point to Before-Save. • Watch for keywords like related records, email alert, subflow, or Apex action — these point to After-Save. • If a question asks which flow type can call the full range of actions, the answer is After-Save. • Eliminate distractors by checking whether the scenario needs an existing record Id; if so, After-Save applies. • Read scenarios carefully: a question may combine requirements, and the presence of any related-record or action requirement means you should choose After-Save.
