Choose a before-save flow when you only need to set or validate fields on the record that triggered the flow before it is saved. Choose an after-save flow when the work needs the saved record’s ID, changes other records, or performs actions such as sending email or calling an external system. In Flow Builder, these options are called Fast Field Updates and Actions and Related Records, respectively.
Make the choice by asking what the flow must do
Use this quick test: does the automation only need to change or validate the triggering record before the initial save? If so, choose before-save. Does it need the record’s ID, a value populated after saving, an update to another record, or an action beyond changing the triggering record? Choose after-save.
As an Amazon Associate I earn from qualifying purchases.
This is a capability decision, not a general preference for one mode. The right timing depends on the work the flow must perform.
Free tools Windows power users keep installed
One-click scans. No signup required.
Compare the two flow options
| Decision point | Before-save: Fast Field Updates | After-save: Actions and Related Records |
|---|---|---|
| When it runs | Before Salesforce saves the triggering record. | After Salesforce saves the record and assigns its ID. |
| Best fit | Set or validate fields on the triggering record. | Work involving other records or actions beyond updating the triggering record. |
| Triggering record ID | Not available yet. | Available. |
| Changing the triggering record | Use Assignment to change $Record; Salesforce applies the values as part of the initial save. |
Use Update Records; the change requires another save operation. |
| Blocking an invalid save | Can show an error and prevent the save. | The triggering record has already been saved when the flow runs. |
| Related records and actions | Cannot update related records or perform other actions in this optimization. | Can create or update records and perform supported actions, such as sending email. |
| Post-save system values | Values populated only after saving, such as Created Date and Last Modified Date, are unavailable. | Post-save values are available. |
| Supported elements | Assignment, Decision, Get Records, and Loop. | A broader set, including Create Records, Update Records, Send Email, and subflows. |
Sources: Salesforce’s before-save and after-save decision guide and record-triggered flow considerations. Available operations can depend on flow type, configuration, permissions, and platform behavior; check the current Help page for your setup.
#1 Best Overall
When a before-save flow is the right fit
Change fields on the triggering record
For a field update that belongs on the record being created or changed, use Assignment to set the relevant $Record fields. Salesforce includes those changes in the initial save, so you do not need an Update Records element just to save the triggering record’s new values.
Reject data before it is committed
Choose before-save when invalid data must stop the save. The flow can show an error before the record is committed. An after-save flow cannot serve as the same pre-commit gate because the record has already saved by the time that flow runs.
Keep the flow within its supported scope
Fast Field Updates supports Assignment, Decision, Get Records, and Loop. It is intended for work on the triggering record, not for creating or updating related records or performing actions such as sending email.
Recommended Free Tools
When an after-save flow is required
Use the saved record’s ID or post-save values
After-save runs once the triggering record has been saved and assigned an ID. Use it when later work needs that ID or a system-populated value that does not exist before the save.
Create or update other records
Use after-save when the flow needs to create a follow-up task, update a related record, or otherwise use the saved record as context for work on another record. These operations require the broader capabilities available to after-save flows.
Perform an action beyond updating the triggering record
Actions such as sending email or calling an external system point to after-save. Salesforce’s comparison guide describes after-save as the choice for work beyond what before-save can do.
Account for the extra save and automation timing
A before-save assignment to the triggering record is incorporated into its initial save. An after-save change to that same record uses Update Records and requires another save operation. That is a concrete difference in the automation path, not a guarantee that every before-save flow will outperform every after-save flow in every org.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesSalesforce states that a record-triggered flow can update a Salesforce record “10 times faster than a record-change process.” The Help page gives no publication year for that claim, and the comparison is with a record-change process—not a universal benchmark comparing all before-save flows with all after-save flows. The practical reason to favor before-save for same-record field updates is that it avoids an additional save and another round of automation.
Best Value
Salesforce also warns that record-triggered flows can behave differently from similar workflow rules because they occupy a different position in the order of execution. When flows interact with other automation, test the actual behavior in the target org rather than assuming that similar-looking rules run at the same point.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Set the trigger and entry conditions deliberately
In the Start element, select the object and the create, update, or delete event that should launch the flow, then set entry conditions to limit which records or transitions run. Activated record-triggered flows can run for changes made through the Salesforce UI, spreadsheet imports, or API integrations, so do not assume the flow is UI-only.
Salesforce’s considerations page identifies a View All Data permission requirement for activating a triggered autolaunched flow in the context described there. Confirm the current requirement for your flow and org in Salesforce’s record-triggered flow considerations before activation.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Designing a flow that needs both kinds of work
Some automation needs to update a triggering record efficiently and then do related work. Separate those responsibilities according to timing: use before-save for eligible field changes to the triggering record, and after-save for work that needs the saved record, its ID, related-record changes, or other actions. There is no universal recipe for every mixed case; account for order of execution and possible recursion, and test the combined automation in the target org.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
