Workflow Action
A Workflow Action is an automated action that runs when a Salesforce workflow rule's criteria are met.
Definition
A Workflow Action is an automated action that runs when a Salesforce workflow rule's criteria are met. There are four kinds: a field update, an email alert, a task, and an outbound message. A workflow rule can fire its actions right away, or queue them as time-dependent actions that wait until a date you specify.
Workflow Actions belong to Workflow Rules, which are now legacy automation. Salesforce ended support for Workflow Rules on December 31, 2025, so it builds no new features or bug fixes for them. Existing actions keep running, but Salesforce recommends rebuilding them in Flow using the Migrate to Flow tool.
The four action types and how they fire
How a workflow action connects to its rule
A workflow action never runs on its own. It is always attached to a workflow rule, which watches one object and defines the criteria that decide when to act. When a record is created or edited and the criteria evaluate to true, the rule fires its actions. You build both pieces under Setup, in Process Automation, where Workflow Rules and the action library live side by side. One action can be reused across several rules, which kept orgs tidy in the workflow era. An email alert that notifies a sales manager, for example, can be referenced by three different rules without rebuilding it each time. The rule supplies the trigger and the timing. The action supplies the work. This separation is the main reason the word "action" exists as its own concept rather than folding into the rule itself. It also explains why deleting a rule does not delete its actions; they sit in a shared pool and can outlive any single rule that used them.
Field updates: changing data automatically
A field update action sets a field to a new value when the rule fires. It can change a field on the record that triggered the rule, or on the parent record across a master-detail relationship. The new value can be a fixed entry, a formula, or a checkbox toggle. Common uses include stamping a status field, flagging a record as reviewed, or recalculating a value when related data changes. Field updates carry behavior that often surprises people. After a field update runs, the platform can re-evaluate the same workflow rules on that record, which sometimes causes a second round of actions. You also choose whether the update should re-run validation rules and other workflow rules, an option set per field update. Because the update happens after the record saves, it runs as part of the same transaction but can shift the final stored values. When you later move this logic to Flow, a record-triggered flow handles the same job with clearer control over before-save versus after-save timing, which removes much of this guesswork.
Email alerts and tasks: notifying people
An email alert sends a templated email to recipients you pick when the rule fires. Recipients can be users, roles, public groups, the record owner, or email addresses stored in fields. The alert relies on a Classic email template, and the body is fixed at design time apart from merge fields. Teams used alerts to tell a manager about a new high-value opportunity, or to confirm a case had been escalated. A task action creates a Salesforce task assigned to a user, role, or the record owner when the rule fires. You set the subject, status, priority, and a due date that can be relative to a date on the record. The task lands in the assignee's list so follow-up work is not forgotten. Both action types share a limit worth knowing: they cannot branch. A workflow rule fires the same alert or task every time its criteria are met, with no "if this, send that, otherwise send something else" logic. Flow lifts that ceiling, letting one flow decide between different emails or tasks based on the record.
Outbound messages: talking to other systems
An outbound message sends record data to an external endpoint when the rule fires. It is a SOAP message in XML, posted over HTTPS to a URL you configure. The message carries the fields you select plus a session ID, so the receiving system can call back into Salesforce if it needs more data. No code runs inside Salesforce; the platform just hands the data off. This made outbound messages a lightweight way to push updates to a middleware tool or an external app without writing Apex. A common pattern sent a notification to an ERP system whenever an order record reached a certain stage. The trade-offs are real, though. The endpoint must speak SOAP, the message format is fixed, and retries follow Salesforce's own schedule rather than yours. Modern integrations usually prefer Platform Events, the External Services REST callouts, or a flow that calls an Apex action, all of which give finer control. Outbound messages still work, but they show their age next to those options.
Immediate versus time-dependent actions
Workflow actions fire in one of two ways. Immediate actions run as soon as the record meets the rule's criteria. Time-dependent actions wait. You attach them to a time trigger defined as a number of days or hours before or after a date field on the record, with a valid range of 0 to 999. A rule might send a reminder email three days before a contract renewal date, for example. The queued actions behave as a batch, not as independent items. Salesforce groups time-dependent actions and starts running the batch within an hour of the first one becoming due, and real execution can lag based on service load. If you edit a date field that an unfired trigger points to, Salesforce recalculates when that trigger should fire. There are guardrails too: removing every action from a time trigger does not delete the trigger, and empty triggers still count against the hourly time-trigger limit. Time-dependent workflow was a popular feature, and reproducing it is exactly what the Migrate to Flow tool handles when it converts scheduled paths into a flow.
Why it is legacy and what replaces it
Salesforce ended support for Workflow Rules and Process Builder on December 31, 2025. Support ending does not mean the lights go out. Active rules and their actions keep running, and you can still activate, deactivate, and edit them. What stops is new investment: no new features and no bug fixes. For any new automation, Salesforce points you to Flow Builder, its low-code, extensible automation tool. Flow covers everything a workflow action did and more. A record-triggered flow replaces field updates and gives you before-save speed. Flow can send emails, create tasks, branch with decisions, loop over records, and call out to other systems, none of which a single workflow rule could do. To ease the move, Salesforce ships the Migrate to Flow tool, which converts workflow rules, including their immediate and scheduled actions, into flows you can review before activating. The practical plan for most orgs is to inventory their workflow actions, migrate the ones that still matter, and build anything new in Flow from the start.
Working with a workflow action in a legacy org
Workflow actions are legacy and new orgs should build in Flow instead. If you still maintain an org with active workflow rules, here is how the pieces fit together when you create or edit a workflow action under Setup.
- Open Workflow Rules
In Setup, go to Process Automation, then Workflow Rules. Pick the object you want to automate, or open an existing rule to manage its actions.
- Choose immediate or time-dependent
Decide whether the action should run the moment criteria are met (immediate) or wait on a time trigger tied to a date field. Add a time trigger first if you need the delayed path.
- Add the action
Use Add Workflow Action to create a new field update, email alert, task, or outbound message, or select an existing action from the shared library to reuse it.
- Activate and test
Save and activate the rule. Edit a sample record so it meets the criteria, then confirm the field changed, the email arrived, the task appeared, or the endpoint received the message.
Sets a field on the record or its master record to a new value, formula, or checkbox state; can re-run other rules.
Sends a Classic email template to chosen users, roles, groups, the owner, or email fields.
Creates a follow-up task with subject, priority, and a due date that can be relative to a record date.
Posts selected fields and a session ID as a SOAP XML message to an external HTTPS endpoint.
- Workflow Rules lost Salesforce support on December 31, 2025; build new automation in Flow, not here.
- Field updates can silently re-trigger workflow rules, causing a second round of actions you did not expect.
- Email alerts and tasks cannot branch; the rule fires the same action every time, so conditional logic needs Flow.
- Empty time triggers still count against the hourly time-trigger limit even after you remove their actions.
Trust & references
Cross-checked against the following references.
Straight from the source - Salesforce's reference material on Workflow Action.
- Workflow RulesSalesforce
- Outbound Message ActionsSalesforce
Hands-on resources to go deeper on Workflow Action.
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 a Workflow Action?
Q2. What are the four types?
Q3. What replaces them?
Discussion
Loading discussion…