Final Approval Actions
Final Approval Actions in Salesforce are the actions that fire automatically when a record completes an Approval Process with a positive outcome.
Definition
Final Approval Actions in Salesforce are the actions that fire automatically when a record completes an Approval Process with a positive outcome. The Approval Process configuration defines what happens at the moment of final approval: update fields on the record (Status = Approved, Locked = True), send Email Alerts to stakeholders, create follow-up Tasks, send Outbound Messages to external systems. Final Approval Actions are distinct from per-step actions (which fire at each approval step) and from Final Rejection Actions (which fire when the approval ends in rejection).
Final Approval Actions are the way an Approval Process tells the rest of Salesforce that a decision is final. The configurations live on the Approval Process detail page in Setup, alongside Initial Submission Actions, Final Rejection Actions, and Recall Actions. Each action is reusable: the same Email Alert can fire from Final Approval Actions, from Workflow Rules, and from Process Builder. The Approval Process orchestrates them in the right context.
How Final Approval Actions work
The four lifecycle moments of an Approval Process
Approval Processes have four moments where automated actions fire: Initial Submission (record submitted for approval), per-step approval (each step approves), Final Approval (the process completes with approval), Final Rejection (the process ends with rejection), and Recall (the submitter recalls the pending approval). Each moment supports its own action set; Final Approval Actions are one of these.
Action types
Final Approval Actions can include: Field Update (change one or more fields on the record), Email Alert (send a pre-configured email), Task (create a follow-up Task related to the record), Outbound Message (send a SOAP message to an external system). These are the same action types available to Workflow Rules; the Approval Process reuses them.
Locking the record on Final Approval
A common Final Approval Action is to lock the record. Approval Processes can lock records automatically as a built-in behavior; Final Approval Actions can also explicitly lock through a Field Update on a Locked flag or through Apex. Locked records prevent further edits except by users with override permissions.
Cascading Field Updates
Field Updates in Final Approval Actions can chain. A Field Update that changes Status to Approved can trigger a Workflow Rule that fires another Field Update or Email Alert; the platform allows up to 5 levels of cascading updates before halting. This is how Approval Processes integrate with broader automation.
Email Alerts and stakeholder notification
Email Alerts in Final Approval Actions send pre-configured emails when the approval completes. Common recipients: the submitter (your request was approved), the next-in-line owner (you now own this record), the finance team (this expense is approved, please process), the customer (your application has been approved).
Outbound Messages for system integration
Outbound Messages fire SOAP messages to external endpoints when the approval completes. Used to notify external systems: an ERP that an order is approved, a contract management system that a contract has signed off, a finance ledger that an expense is greenlit. Modern integrations more often use Platform Events or REST callouts, but Outbound Messages remain supported.
Final Approval versus per-step Approval Actions
Per-step Approval Actions fire at each step in a multi-step approval; Final Approval Actions fire only when the entire process completes. A 3-step approval has three sets of per-step Actions and one set of Final Approval Actions. Use per-step for intermediate notifications (Step 2 approved, now waiting on Step 3); use Final Approval for end-state actions.
How to configure Final Approval Actions
Configuring Final Approval Actions is done on the Approval Process detail page in Setup. The configuration includes selecting the action types, defining each action, and specifying when they fire.
- Open the Approval Process
Setup, then Approval Processes, then the process you want to configure. The detail page shows the lifecycle moments including Final Approval Actions.
- Navigate to Final Approval Actions section
Scroll to Final Approval Actions on the Approval Process detail page. Click Add Existing or Add New to create or attach actions.
- Add Field Updates
Common pattern: update Status to Approved, set ApprovedDate to TODAY, set ApprovedBy to the running user. Configure the field, the new value (literal, formula, or merge field), and any reevaluation behavior.
- Add Email Alerts
Pick existing Email Alerts or create new ones. Configure the recipients (Roles, Public Groups, Users, record email fields). Pick the Email Template that defines the message content.
- Add Tasks if needed
Create follow-up Tasks: assign to the appropriate user, set the Subject and Due Date. Tasks created here appear in the assignee''s task list.
- Save and test the Approval Process
Save the configuration. Submit a test record through the Approval Process and complete each step. Verify the Final Approval Actions fire correctly at the moment of final approval.
Modify fields on the record at the moment of final approval. Most common Final Approval Action.
Send a pre-configured email to stakeholders.
Create a follow-up Task related to the record.
Send a SOAP message to an external system. Legacy integration pattern.
- Final Approval Actions fire only once when the process completes. They do not fire per step; use per-step actions for that.
- Field Updates can trigger downstream Workflow Rules. Plan the cascade carefully; circular updates are blocked at 5 levels.
- Locked records cannot be edited even by the record owner without unlock permission. Make sure unlock workflows exist for emergency edits.
- Outbound Messages are SOAP-based. Modern integrations should use Platform Events or REST callouts; OMs are kept for backward compatibility.
Trust & references
Straight from the source - Salesforce's reference material on Final Approval Actions.
- Approval Process ActionsSalesforce Help
Hands-on resources to go deeper on Final Approval Actions.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is the main advantage of using Final Approval Actions over writing Apex code?
Q2. Which Salesforce tool has Salesforce recommended as the future of automation?
Q3. What type of Salesforce feature is Final Approval Actions?
Discussion
Loading discussion…