Immediate Action
In Salesforce Process Builder and workflow rules, an action that executes right away when the trigger criteria are met, as opposed to time-dependent actions that are scheduled for a future date.
Definition
In Salesforce Process Builder and workflow rules, an action that executes right away when the trigger criteria are met, as opposed to time-dependent actions that are scheduled for a future date.
In plain English
“An Immediate Action in Process Builder or workflow rules is an action that runs right away when the trigger fires. It's the opposite of a time-dependent action, which gets scheduled for some future date. Most automation actions are immediate.”
Worked example
Brookwood Software's Process Builder process on the Lead object fires when Lead Status changes to "Qualified." Two Immediate Actions execute right away: a Field Update sets the Lead's Conversion_Date__c to today, and an Email Alert notifies the AE that their assigned lead is ready. A separate Time-Dependent Action is scheduled for 7 days later (a follow-up reminder if the AE hasn't logged activity). Immediate Actions handle the synchronous side effects of the trigger; time-dependent actions handle the deferred ones. Most automation actions are Immediate.
Why Immediate Action matters
In Salesforce Process Builder and workflow rules, an Immediate Action is an action that executes right away when the trigger criteria are met, as opposed to time-dependent actions that are scheduled for a future date. Most automation actions fall into the immediate category: field updates, email alerts, task creation, outbound messages all typically fire immediately when the rule criteria are satisfied.
The distinction between immediate and time-dependent actions matters for designing automation that responds to events at the right moment. Immediate actions handle 'when this happens, do that' scenarios. Time-dependent actions handle 'X days after this happens, do that' scenarios, like sending reminder emails 3 days after a case is opened. With Workflow Rules and Process Builder being deprecated in favor of Flow, the same concepts exist in Flow as immediate-running actions versus scheduled paths. Knowing about Immediate Actions matters for understanding legacy automation; new automation should use Flow's terminology.
How to set up Immediate Action
Immediate Actions are the fire-right-now actions in Workflow Rules and (legacy) Process Builder — Field Updates, Email Alerts, Tasks, Outbound Messages that execute as soon as the rule's criteria match. Distinct from Time-Dependent Actions which queue and fire later. Configured per Workflow Rule under the Immediate Workflow Actions section.
- Open Setup → Workflow Rules → click into a Rule
Immediate Actions are per-rule. New Workflow Rules in modern orgs are blocked — this applies to existing rules.
- Scroll to Immediate Workflow Actions section
First section below the rule criteria.
- Click Add Workflow Action → pick type
Field Update / Email Alert / Task / Outbound Message. Each configures the same way as Time-Dependent.
- Configure the action
Field Update: pick field + new value. Email Alert: pick template + recipients. Task: subject + assignee. Outbound Message: endpoint + fields to include.
- Save the action
Multiple actions allowed; fire in order. Order is fixed at creation, not editable.
- Activate the parent Workflow Rule
Inactive rules don't fire; therefore inactive immediate actions don't fire either.
Field Update / Email Alert / Task / Outbound Message.
Fixed at action creation — not editable after.
Re-fire workflow on the updated field. Risk of recursion.
- Immediate Actions in Workflow Rules are legacy. Modern Salesforce blocks new Workflow Rules — use Flow Builder's record-triggered flows for new immediate-action automation.
- Order of actions within a rule is set at creation. To re-order, you must delete and recreate — careful with reordering live rules.
- Re-evaluate Workflow Rules can recurse. A Field Update that re-triggers the same rule (or another rule with overlapping criteria) creates a loop. Test thoroughly.
How organizations use Immediate Action
Migrated their old Workflow Rule immediate actions to Flow Record-Triggered automation, where actions fire immediately when triggers match.
Uses Flow's scheduled paths for time-dependent automation that previously would have used time-dependent workflow actions.
Treats Workflow Rules immediate actions as legacy code; new automation goes directly into Flow.
Test your knowledge
Q1. What is an Immediate Action?
Q2. Where do Immediate Actions appear?
Q3. Where should new immediate automation be built?
Discussion
Loading discussion…