Before-Save vs After-Save Flows: What You Need to Know

Best for: Fast field updates on the same record.

• Super-fast execution
• Only allows field updates to the triggering record
• Cannot create related records
• Cannot invoke actions (e.g., email alerts, Apex, DML)
• No access to the record after it’s saved

Examples:

• Auto-fill a field based on another value (e.g., set Status = ‘New’ if Priority = ‘High’)
• Calculate a discount based on a picklist value
• Set a record owner based on region
• Default values before save

Why use Before-Save Flow

• 10x faster than after-save flows for field updates
• Reduces need for Apex code
• No additional DML operations required

Best for: Complex logic, DML, and external operations.

• Can access the record after save
• Can create/update/delete related records
• Can call Apex, send emails, and submit for approval
• Can access related record values using Get Records or $Record > Relationship.Field

Examples:

• Create a related Contact when an Account is created
• Send a welcome email when a user signs up
• Create a task when an Opportunity is moved to “Closed Won”
• Update a parent record based on child changes.
• Can’t update the same record that triggered the flow directly (you’ll need another DML).
• Adds extra overhead if used incorrectly

Why use After-Save Flow

• Allows creation or update of related records
• Can send email alerts, post to Chatter, or call Apex
• Supports access to the record ID and related objects
• Enables complex automation and multi-record processing
• Ideal for actions that require data to be committed first

• Use Before-Save whenever possible for basic field updates.
• For related object changes or external calls, use After-Save.
• Avoid updating the same record in an After-Save flow to prevent recursion.
• Keep your flows modular — split complex logic across multiple flows if needed.
• Use Decision elements wisely — unnecessary checks slow down the flow.

Use Case 1: Auto-assign Priority

• Object: Case
• Logic: If Type = High, set Priority = P1
• Before-Save (Simple field update)

Use Case 2: Create Task on Opportunity Closed

• Object: Opportunity
• Logic: When Stage = Closed Won, create follow-up Task
• Best Flow: After-Save (Related record creation)

Ask yourself these key questions:

• Just updating the current record? → Use a Before-Save Flow
  
• Need to create/update other records or send emails? → Use an After-Save Flow
  
• Need performance and want to avoid extra DML? → Use Before-Save
  
• Need full access to record context or Salesforce ID? → Go with After-Save

• Use before-save for fast, in-memory field updates on the triggering record
• Use after-save for complex logic involving related objects, record creation, or notifications