Workflow Rules
Learning Content
Last updated: July 21, 2026
Workflow Rules
A Workflow Rule is a declarative Salesforce automation feature that automatically performs predefined actions when specific criteria are met. Workflow Rules were one of Salesforce's earliest automation tools and have been widely used to update fields, send email alerts, create tasks, and send outbound messages.
Although Workflow Rules continue to function in existing Salesforce organizations, Salesforce recommends using Record-Triggered Flows for new automation because they provide greater flexibility and support more advanced business processes.
💡 LearnFrenzy Insight
Think of Workflow Rules as an automatic office assistant.
Whenever a document meets certain conditions, the assistant updates a status, sends an email, creates a follow-up task, or notifies another system.
Workflow Rules perform these repetitive business actions automatically without requiring Apex code.
Where Do Workflow Rules Execute?
Database Save
│
▼
After Trigger
│
▼
Assignment Rules
│
▼
Auto-Response Rules
│
▼
Escalation Rules
│
▼
⭐ Workflow Rules
│
▼
Record-Triggered Flow
│
▼
Roll-Up Summary
│
▼
Commit Transaction
Workflow Rules execute after the record has been saved and after standard platform automation such as Assignment Rules and Auto-Response Rules. If the workflow updates the same record, Salesforce may perform an additional save cycle, causing parts of the Order of Execution to run again.
What Can Workflow Rules Do?
| Workflow Action | Description |
|---|---|
| Field Update | Automatically update field values. |
| Email Alert | Send notification emails. |
| Create Task | Create follow-up activities. |
| Outbound Message | Send SOAP-based messages to external systems. |
Workflow Rule Evaluation
| Evaluation Option | Description |
|---|---|
| Created | Runs only when the record is created. |
| Created and Every Edit | Runs whenever the criteria are met. |
| Created and Edited to Meet Criteria | Runs only when the record changes from not meeting to meeting the criteria. |
Real Business Scenario
🏢 Business Example
Whenever an Opportunity reaches the Closed Won stage:
- Update the Status field.
- Create a follow-up Task for the implementation team.
- Send an email notification to the Sales Manager.
- Notify an external ERP system using an Outbound Message.
Traditionally, many Salesforce organizations implemented this type of automation using Workflow Rules.
Workflow Rule vs Record-Triggered Flow
| Feature | Workflow Rule | Record-Triggered Flow |
|---|---|---|
| Status | Legacy | Recommended |
| Supports Multiple Objects | Limited | Yes |
| Decision Logic | Basic | Advanced |
| Loops | No | Yes |
| Create Records | No | Yes |
| Update Related Records | Limited | Yes |
| Future Investment | Maintenance Only | Strategic Automation Platform |
When Should You Use Workflow Rules?
| Use Workflow Rules | Prefer Record-Triggered Flow |
|---|---|
| Maintaining existing legacy automation. | Building new automation. |
| Supporting older Salesforce implementations. | Complex business logic. |
| Minor enhancements to existing Workflow. | Cross-object automation. |
| Simple email alerts in legacy orgs. | Future-proof enterprise solutions. |
🔍 Behind the Scenes: What Happens Internally?
After Trigger Completes
│
▼
Workflow Rule Evaluated
│
▼
Criteria Met?
Yes │ No
│
▼
Execute Workflow Action
│
▼
Field Updated?
Yes │ No
│
▼
Record May Enter Another Save Cycle
│
▼
Continue Order of Execution
One important characteristic of Workflow Rules is that a workflow field update can cause Salesforce to perform another save cycle. This means portions of the Order of Execution may execute again, which developers must consider when designing automation to avoid unintended behavior.
Why Understanding Workflow Rules Still Matters
| Reason | Explanation |
|---|---|
| Legacy Orgs | Many production orgs still use Workflow Rules extensively. |
| Interview Preparation | Frequently compared with Record-Triggered Flows. |
| Migration Projects | Organizations are gradually replacing Workflow Rules with Flows. |
| Execution Flow Knowledge | Understanding Workflow behavior helps explain recursive save cycles. |
✅ Best Practice
Do not create new Workflow Rules unless you have a compelling reason to extend existing legacy automation. For new development, use Record-Triggered Flows because they provide significantly more flexibility, maintainability, and long-term platform support.
⚠️ Common Mistake
Assuming Workflow Rules are obsolete and can be ignored. Although Salesforce recommends Flow for new automation, many enterprise organizations still rely on Workflow Rules, so developers must understand how they behave during the Order of Execution.
🎯 Interview Tip
Question: Why can a Workflow Rule sometimes cause another execution cycle?
Answer: If a Workflow Rule performs a field update, Salesforce saves the modified record again. This additional save can cause parts of the Order of Execution, such as validation, triggers, and workflow evaluation, to run again depending on the circumstances.
- ✔ Legacy declarative automation feature.
- ✔ Executes after After Triggers and standard platform rules.
- ✔ Can update fields, send emails, create tasks, and send outbound messages.
- ✔ Field updates may trigger another save cycle.
- ✔ Salesforce recommends Record-Triggered Flow for new automation.
- ✔ Still important for maintaining legacy Salesforce implementations.
➡ Next Lesson
In the next lesson, you'll learn about Process Builder (Legacy), why it was introduced after Workflow Rules, how it differs from Workflow, and why Salesforce now recommends Record-Triggered Flows instead.
Practice What You've Learned
Test your understanding with these practice exercises