Automated Actions
Automated Actions in Salesforce are the side effects that automation tools fire when their triggering conditions are met.
Definition
Automated Actions in Salesforce are the side effects that automation tools fire when their triggering conditions are met. Workflow Rules, Approval Processes, and Process Builder all rely on a fixed set of Automated Actions: Field Update (change a field on the triggering record or its parent), Email Alert (send an outbound email using a template), Task (create an assigned Task record), Outbound Message (post a SOAP message to a configured remote endpoint). Each Automated Action is a metadata record reused across multiple automation rules; the action is configured once in Setup and referenced wherever it should fire.
The Automated Actions concept predates Flow. As Salesforce consolidated automation around Flow, most new development uses Flow Actions (the equivalent inside Flow Builder) rather than the legacy Automated Actions surface. Workflow Rules have been retired. Process Builder is in maintenance mode. Approval Processes still expose Automated Actions for backward compatibility, and existing Workflow Rule actions continue to function in legacy orgs. New automation should use Flow with its richer set of action types (Apex Actions, External Services, HTTP Callouts, sub-flows) rather than the legacy four-action menu.
The legacy Automated Actions and their Flow successors
Field Update
Field Update Actions change a field value on the triggering record (or its parent for related records). Workflow Rules used Field Updates extensively for status transitions, formula recalculations, and parent-record propagation. Modern Flow replaces this with Update Records elements that support the same operations plus loops, decisions, and any-record-set scope.
Email Alert
Email Alert Actions send outbound emails using a chosen Email Template, addressed to a chosen recipient set (user, role, queue, email field on the record). Modern Flow replaces this with the Send Email element that supports the same templates plus rich Lightning Email composition.
Task
Task Actions create a new Task record assigned to a chosen user, queue, or related-user lookup. Modern Flow Create Records achieves the same with more flexibility in field assignments and conditional creation.
Outbound Message
Outbound Message Actions post a SOAP message to a configured remote endpoint when fired. The pattern is legacy and brittle; modern integrations use Flow plus HTTP Callout, Platform Events, or Change Data Capture instead. Existing Outbound Messages continue to work but new development should not add them.
How Automated Actions appear in each automation tool
Workflow Rules: Add an Action to a rule, pointing at any of the four. Approval Processes: Initial Submission, Approval Step, Final Approval, Final Rejection, and Recall trigger points each accept Automated Actions. Process Builder: each Process step adds an Action of the same type set, plus additional types Flow inherited (Apex, Submit for Approval, Post to Chatter). Flow extends the list further with Apex Actions and External Services.
Why Salesforce moved automation to Flow
Each legacy automation tool maintained its own action catalogue and its own runtime characteristics. Consolidating around Flow gave admins one canvas, one debugger, and one set of actions. Workflow Rules retirement and Process Builder deprecation followed. Automated Actions remain only because Approval Process and legacy Workflow Rules still expose them.
Migrating Automated Actions to Flow
Salesforce ships a Migrate to Flow tool that converts Workflow Rules and Process Builders into equivalent Record-Triggered Flows. Field Updates become Update Records elements, Email Alerts become Send Email elements, Tasks become Create Records elements. The tool handles common patterns; manual cleanup follows for complex rules.
Common gotchas
Three patterns recur. Field Updates with Re-evaluate Workflow Rules turned on can produce loops. Email Alerts addressed to the running user fire surprisingly often when automation chains. Outbound Messages without monitoring fail silently when the remote endpoint goes down. Replace with Flow plus explicit error handling whenever possible.
How to migrate Automated Actions to Flow
Salesforce's Migrate to Flow tool handles most of the mechanics. The remaining work is reviewing the converted flows for clarity, naming, and error handling.
- Inventory existing Automated Actions
List every Workflow Rule, Process Builder, and Approval Process Action. Group by automation tool and impact.
- Run Migrate to Flow per Workflow Rule
Setup, search for Migrate to Flow. Pick a Workflow Rule or Process Builder. The tool generates an equivalent Record-Triggered Flow.
- Review the converted Flow
Check element naming, decision logic, and fault paths. Rename auto-generated elements for clarity. Add error logging.
- Test in sandbox
Use Flow Debug with sample data, then run integration tests in the sandbox. Confirm parity with the legacy behaviour before activating.
- Deactivate the legacy automation
Once the new Flow is active and validated, deactivate the original Workflow Rule or Process Builder. Keep them inactive (not deleted) for one release in case rollback is needed.
- Field Updates with Re-evaluate Workflow Rules turned on can produce loops. Flow conversion preserves the setting; audit before activation.
- Outbound Messages do not have a direct Flow equivalent. Replace with Flow plus HTTP Callout or a Platform Event publish.
- Approval Process Automated Actions are still supported. They have not been migrated to Flow-only yet, so existing Approval Process automation continues to work.
- Email Alerts assigned to user lookup fields require those lookups to be populated. Empty fields silently send no email.
Trust & references
Cross-checked against the following references.
- Workflow Rules and ActionsSalesforce Help
- Migrate to Flow OverviewSalesforce Help
Straight from the source - Salesforce's reference material on Automated Actions.
- Flow OverviewSalesforce Help
Hands-on resources to go deeper on Automated 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 are the four classic Automated Action types?
Q2. Which tools use Automated Actions?
Q3. What is the modern replacement for classic Automated Actions?
Discussion
Loading discussion…