Workflow Action
An automated action configured in a Salesforce workflow rule that executes when the rule's criteria are met, including field updates, email alerts, task creation, and outbound messages to external systems.
Definition
An automated action configured in a Salesforce workflow rule that executes when the rule's criteria are met, including field updates, email alerts, task creation, and outbound messages to external systems.
In plain English
“A Workflow Action is an automated action in a Salesforce workflow rule that fires when criteria are met. The four types are field updates, email alerts, task creation, and outbound messages. Workflow Rules are legacy; Flow is the modern replacement.”
Worked example
A legacy Workflow Rule at Brookwell Capital fires when a Case is escalated. The rule is configured with three Workflow Actions: a Field Update to set Status = "Escalated," an Email Alert to the support VP, a Task assigned to the Tier 3 queue. Workflow Actions are the four primitives the platform offers (Field Update, Email Alert, Task, Outbound Message) - the discrete "things that happen" when rules fire. With Workflow Rules retired in favor of Flow, the same Workflow Actions translate to Flow elements during migration.
Why Workflow Action matters
A Workflow Action is an automated action configured in a Salesforce workflow rule that executes when the rule's criteria are met, including field updates, email alerts, task creation, and outbound messages. These four action types cover the basic automation patterns.
Workflow Actions are part of legacy Workflow Rules. Salesforce is retiring Workflow Rules, so all workflow actions should be migrated to Flow, which provides the same capabilities plus much more flexibility. Mature orgs plan migration from workflow actions to Flow actions.
How to set up Workflow Action
Workflow Actions are the things a Workflow Rule does when it fires — Field Update / Email Alert / Outbound Message / Task. They're configured per Workflow Rule under Immediate Actions or Time-Dependent Actions. Salesforce has retired Workflow Rules for new automation in favor of Flow; existing actions still work but new development should use Flow.
- Open Setup → Workflow Rules → click into a Rule
Workflow Actions are configured per Workflow Rule, not standalone.
- Pick Immediate vs Time-Dependent Actions
Immediate fires when the rule's criteria match. Time-Dependent fires X days/hours later, queued in the Time-Based Workflow Queue.
- Click Add Workflow Action → pick type
Field Update / Email Alert / Task / Outbound Message. Each has its own configuration form.
- Configure the action
Field Update: pick field + value. Email Alert: pick template + recipients. Task: subject + assignee. Outbound Message: endpoint + fields.
- Save the action
Action is now part of the rule. Multiple actions per rule are allowed — they fire in order.
- Activate the parent Workflow Rule
Inactive rules don't fire; therefore inactive actions don't fire either.
Field Update / Email Alert / Task / Outbound Message.
Fire now or schedule for later.
Allowed; fire in order.
- Workflow Rules are retired for new automation in modern Salesforce. New Field Updates / Email Alerts should be in Flow Builder. Workflow Actions still exist on legacy rules but won't see new features.
- Time-Dependent Actions queue in the Time-Based Workflow Queue. Editing the parent record may move or remove queue entries depending on Re-Evaluate Workflow Rules behavior.
- Field Updates from Workflow Actions can re-fire Workflow Rules if Re-Evaluate is on. Risk of recursion — keep this off unless intentional.
How organizations use Workflow Action
Migrates legacy workflow actions to Flow.
Uses Flow for all new automation, replacing workflow actions.
Treats workflow action references as migration candidates.
Trust & references
Straight from the source - Salesforce's reference material on Workflow Action.
- Workflow RulesSalesforce Help
Test your knowledge
Q1. What is a Workflow Action?
Q2. What are the four types?
Q3. What replaces them?
Discussion
Loading discussion…