Immediate Action
An Immediate Action is a type of Workflow Rule action in Salesforce that runs the moment the rule's criteria evaluate to true, inside the same transaction as the record save that triggered it.
Definition
An Immediate Action is a type of Workflow Rule action in Salesforce that runs the moment the rule's criteria evaluate to true, inside the same transaction as the record save that triggered it. It sits on a Workflow Rule next to Time-Dependent Actions, which wait until a future point before they fire. The four action types you could attach as an Immediate Action were Field Update, Email Alert, Task, and Outbound Message.
Workflow Rules are now legacy. Salesforce ended support for Workflow Rules and Process Builder on December 31, 2025, and the recommended replacement is a record-triggered flow built in Flow Builder. Existing rules keep running and you can still edit them, but no support or bug fixes are provided. The Immediate Action term still matters for orgs on legacy automation, for reading Migrate to Flow output, and for understanding older certification material, so it is worth knowing even though no new automation should be designed around it.
Understanding Immediate Actions and their move to Flow
How an Immediate Action fired inside a Workflow Rule
A Workflow Rule was attached to one object and ran on record create, or on create and every edit, depending on its evaluation setting. When a record was saved, Salesforce checked the rule's criteria. If the criteria were true, every Immediate Action on that rule ran right away, in the same save transaction. There was no delay and no queue. You could attach four kinds of action: a Field Update to set a value on the record, an Email Alert to send a templated email, a Task to create a follow-up activity, and an Outbound Message to send a SOAP message to an external endpoint. A single rule could carry several Immediate Actions at once, so one save might update a field, send an alert, and create a task together. Because the work happened in the triggering transaction, the user saw the results as soon as the save finished. This made Immediate Actions the everyday tool for real-time reactions to data changes before Flow Builder existed.
Immediate Actions compared with Time-Dependent Actions
Every Workflow Rule could hold two buckets of automation. Immediate Actions ran at once. Time-Dependent Actions were the same four action types, but scheduled to fire at a defined offset, such as 24 hours after the rule fired or 7 days before a Close Date. Salesforce held those scheduled actions in a workflow queue and processed them when their time arrived. The pairing gave one rule both instant and delayed behavior. There was an important catch with the queue. If a record stopped matching the rule's criteria before a scheduled action ran, Salesforce removed that pending action from the queue. Time-Dependent Actions also required the rule's evaluation to be set to create, or to create and edit when criteria are met, rather than on every edit. Immediate Actions had no such restriction, which is one reason they were far more common in practice than their time-based siblings.
Where Immediate Actions sat in the order of execution
Timing is the detail that trips people up when they compare Workflow Rules to flows. A Workflow Rule, and therefore its Immediate Actions, ran after the record had already been saved to the database but before the transaction committed. A Field Update from a Workflow Rule then issued a second save on that record. This is different from a before-save record-triggered flow, which sets field values during the initial save with no extra update. The difference is not academic. A migrated flow can fire in a different sequence than the original rule, so a value that one piece of automation depended on might not be present at the same moment. Salesforce calls this out directly and recommends using Flow Trigger Explorer to assign priority values so flows run in a predictable order. Anyone converting Immediate Actions needs to test the result rather than assume the behavior is identical.
The 2025 retirement and what replaces it
Salesforce ended support for Workflow Rules and Process Builder on December 31, 2025. The official guidance is plain: active rules and processes keep running as they do today, but customer support is gone and bugs will not be fixed. Salesforce points everyone toward Flow Builder, described as its modern low-code automation tool. A record-triggered flow now does everything a Workflow Rule did and more. It can update the same record, update related records, send emails, create records, and call other automation, all from one builder with branching logic and debug tooling that Workflow Rules never had. There is no separate Immediate Action concept in a flow. You simply add elements that run when the flow is triggered. For delayed behavior, a flow uses a scheduled path, which is the modern stand-in for a Time-Dependent Action. The practical message for admins is to plan migration deliberately because complex orgs need time and testing.
How the Migrate to Flow tool converts Immediate Actions
Salesforce ships a built-in Migrate to Flow tool to move legacy automation. You reach it from Setup by searching Migrate to Flow. You pick a Workflow Rule, run the migration, and the tool produces a record-triggered flow that mirrors the rule, including its Immediate Actions as flow elements. A Field Update becomes an Update Records element, an Email Alert becomes a Send Email Alert action, and the rule's criteria become the flow's entry conditions. The recommended sequence is to migrate, test the new flow in Flow Builder, then deactivate the old rule and activate the flow. Salesforce highlights a real performance gain: turning on Fast Field Updates can make a flow run close to ten times faster than the original Workflow Rule. The conversion is automated but not flawless. Complex Workflow formulas and unusual configurations may not translate cleanly, so the output always needs human review before it goes live.
Why Email Alerts outlived the rules that called them
One piece of the Immediate Action world survived the retirement intact. The Email Alert is a reusable automation component that lives under Process Automation in Setup, separate from any single Workflow Rule. Because it is a standalone object, a flow can call the very same Email Alert through the Send Email Alert action. So when the Migrate to Flow tool converts a rule whose Immediate Action sent an Email Alert, it does not rebuild the email. It reuses the existing alert from the flow. This is why teams that spent years crafting templated alerts did not lose that work when Workflow Rules wound down. Field Updates, by contrast, were configured inside the rule itself and are recreated as flow elements during migration. Knowing which pieces carry over and which are rebuilt helps you predict what a migrated flow will look like and where you need to double-check the result.
Reading the term in legacy orgs and exam prep
The Immediate Action label still shows up in plenty of places. Older Salesforce training, certification study guides, AppExchange managed packages, and inherited orgs all reference it. An admin who takes over an org running dozens of Workflow Rules has to understand Immediate Actions to know what that automation does before deciding how to replace it. The term also appears in the documentation and metadata the Migrate to Flow tool generates, so it remains part of the vocabulary even as the feature retires. For certification, treat it as historical knowledge. Current exams center on record-triggered flows and Flow Builder, and Immediate Actions surface mainly in questions about legacy automation or migration. The safest stance is to recognize the term, understand how it behaved, and steer every new build toward a flow.
Trust & references
Cross-checked against the following references.
Straight from the source - Salesforce's reference material on Immediate Action.
Hands-on resources to go deeper on Immediate 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. When does an Immediate Action on a Workflow Rule fire?
Q2. Which is a typical Immediate Action available on a Workflow Rule?
Q3. When Migrate to Flow converts a Workflow Rule, what becomes of its Immediate Actions?
Discussion
Loading discussion…