If you’re learning Salesforce automation or you’ve recently started working on an existing Salesforce org, you’ve probably heard about three automation tools: Workflow Rules, Process Builder, and Flow Builder.
All three tools are used to automate business processes in Salesforce. They can perform actions automatically when a record is created or updated, or when it meets specific conditions.
However, they were introduced at different times and offer different levels of functionality. Before we compare them in detail, here’s the most important thing to know:
Salesforce has retired Workflow Rules and Process Builder. As of December 31, 2025, these tools are no longer supported for future development. Flow Builder is now Salesforce’s primary and recommended automation tool.
So, why is it still important to learn about Workflow Rules and Process Builder?
- Many Salesforce orgs still have existing Workflow Rules and Process Builder automations that continue to run.
- Salesforce certification exams may still reference these tools.
- Understanding the limitations of older automation tools helps you better understand and use Flow Builder.
- When troubleshooting a legacy Salesforce org, knowing how these tools work can help you identify and resolve issues more effectively.
Now, let’s compare Workflow Rules, Process Builder, and Flow Builder in detail.
How Salesforce Automation Evolved Over Time
Salesforce did not introduce Workflow Rules, Process Builder, and Flow Builder simultaneously. Each tool was created to solve the limitations of the previous one and provide more powerful automation capabilities.
Workflow Rules (Introduced Around 2005)
Workflow Rules was Salesforce’s first automation tool. It allowed admins to automate simple business processes without writing Apex code.
With Workflow Rules, you could:
- Send email alerts
- Update field values
- Create tasks
- Send outbound messages
While it was reliable and easy to use, it had limited functionality and could only handle basic automation requirements.
Process Builder (Introduced in Spring ’15)
Salesforce introduced Process Builder as an enhanced version of Workflow Rules.
It provided a visual interface and allowed admins to build more advanced automation without code. Compared to Workflow Rules, Process Builder could:
- Perform multiple actions from a single process
- Create and update records
- Submit records for approval
- Post to Chatter
- Launch Flows
Because of its drag-and-drop interface and additional capabilities, Process Builder quickly became popular among Salesforce Admins.
Flow Builder (Major Salesforce Focus from 2019 Onwards)
Although Salesforce Flow existed before 2019, it was often considered complex and was mainly used by advanced admins and developers.
Starting around 2019, Salesforce invested heavily in Flow Builder by improving the user interface and adding powerful automation features. This made Flow Builder much easier for admins to learn and use.
Today, Flow Builder can handle almost every automation requirement in Salesforce, including:
- Record-triggered automation
- Scheduled automation
- Screen Flows for user interaction
- Approval process replacements
- Complex business logic
- Integrations with external systems
Because Flow Builder provides far more flexibility and functionality than Workflow Rules and Process Builder, Salesforce has made it the future of automation.
Retirement of Workflow Rules and Process Builder
Salesforce announced the retirement of Workflow Rules and Process Builder and encouraged customers to move their automation to Flow Builder.
Workflow Rules and Process Builder are no longer recommended for building new automations. Salesforce’s focus is now entirely on Flow Builder, and all new automation enhancements are being added to Flow.
While existing Workflow Rules and Process Builder automations may still be running in some Salesforce orgs, Salesforce recommends migrating them to Flow Builder to take advantage of ongoing support, new features, and improved performance.
Today, Flow Builder is the standard automation tool used by Salesforce Admins and Developers.
The Three Tools at a Glance
Before we compare them in detail, let’s understand what each automation tool was designed to do.
Workflow Rules
Workflow Rules were designed for simple automation requirements. The logic was straightforward:
If a record meets specific criteria, perform a predefined action.
Common actions included:
- Sending email alerts
- Updating field values
- Creating tasks
- Sending outbound messages
Workflow Rules were fast and easy to configure, but they were limited to basic automation scenarios.
Process Builder
Process Builder was introduced to provide more flexibility than Workflow Rules.
Using a visual drag-and-drop interface, admins could create automations that:
- Evaluate multiple criteria
- Perform multiple actions
- Create and update records
- Launch Flows
- Submit records for approval
- Post to Chatter
Although Process Builder was more powerful than Workflow Rules, it still had limitations when handling complex business processes.
Flow Builder
Flow Builder is Salesforce’s most powerful automation tool and the future of Salesforce automation.
It can handle everything that Workflow Rules and Process Builder could do, along with many advanced capabilities such as:
- Record-Triggered Flows
- Scheduled Flows
- Screen Flows
- Complex decision logic
- Loops and collections
- Approval process automation
- Error handling
- Integration with external systems
- Custom user interactions
Because of its flexibility and wide range of features, Flow Builder can support both simple and highly complex business processes within Salesforce.
This is the automation platform that Salesforce continues to invest in and expand with new capabilities.
What Each Tool Could (or Can) Do
Now, let’s look at the capabilities of each automation tool and understand how Salesforce automation has evolved over time.
Workflow Rules
Workflow Rules were designed for basic automation and supported only a limited set of actions.
The available actions were:
- Field Update
- Automatically update a field on the record that triggered the workflow. In some scenarios, fields on a parent record could also be updated.
- Email Alert
- Send an email notification to users, roles, or email addresses defined in Salesforce.
- Task Creation
- Automatically create a Task record and assign it to a user.
- Outbound Message
- Send information from Salesforce to an external system using an outbound message.
These were the only actions available in Workflow Rules. You could not create custom records, delete records, call Apex, launch Flows, or perform complex business logic.
One useful feature of Workflow Rules was Time-Based Workflow Actions. For example, you could schedule an email alert to be sent 3 days after a Case was created or update a field after a specific period.
Workflow Rules could only run when a record was created or updated. They could not run on record deletion, on a schedule, from a platform event, or through user interaction.
Process Builder
Process Builder provided much more flexibility than Workflow Rules and allowed admins to build more advanced automation using a visual interface.
Some of the actions available in Process Builder included:
- Create Records
- Create records for any Salesforce object, not just Tasks.
- Update Records
- Update the triggering record, related records, or records connected through relationships.
- Post to Chatter
- Automatically publish posts to a user, group, or record feed.
- Launch a Flow
- Invoke a Flow to handle more advanced automation logic.
- Submit for Approval
- Automatically submit records into an approval process.
- Call Apex
- Execute Apex code when custom business logic is required.
- Send Email Alerts
- Send email notifications based on business conditions.
- Quick Actions
- Execute predefined object-specific actions.
- Send Custom Notifications
- Send in-app or mobile notifications to Salesforce users.
Another major improvement was the ability to use multiple criteria nodes within a single process. This allowed admins to evaluate different business conditions and perform different actions within a single automation.
Although Process Builder was more powerful than Workflow Rules, it still had several limitations:
- Could not trigger when a record was deleted
- Did not support scheduled automation like Scheduled Flows
- Could not efficiently process collections of records using loops
- Had limited error-handling capabilities
- Performance could become slower when many processes exist on the same object
Flow Builder
Flow Builder is Salesforce’s most powerful automation platform and combines the capabilities of Workflow Rules, Process Builder, and many advanced features in a single tool.
Flow Builder supports multiple automation types, including:
- Record-Triggered Flows
- Scheduled Flows
- Screen Flows
- Platform Event-Triggered Flows
- Autolaunched Flows
- Approval Process automation
- Orchestrations
Some of the advanced capabilities available in Flow Builder include:
- Multiple Trigger Options
- Flows can run when records are created, updated, or deleted; on a schedule; in response to platform events; or when users interact with a Screen Flow.
- Loops
- Process collections of records and perform actions on each record within the collection.
- Advanced Decision Logic
- Build complex business logic using multiple decision branches and conditions.
- Create, Update, and Delete Records
- Manage records across Salesforce objects without writing code.
- Fault Paths
- Handle errors gracefully and define actions when a Flow encounters an issue.
- Subflows
- Reuse automation by calling one Flow from another Flow.
- Before-Save Flows
- Update field values before the record is saved to improve performance and reduce resource consumption.
- Screen Flows
- Create interactive forms, guided processes, and user-friendly wizards for Salesforce users.
- Get Records
- Retrieve data from Salesforce objects and use it throughout the Flow.
- Integration Capabilities
- Connect Salesforce with external systems using HTTP Callouts, Apex actions, platform events, and other integration options.
Most importantly, Flow Builder can do virtually everything Workflow Rules and Process Builder can, while also supporting more complex business requirements and modern Salesforce automation practices.
For this reason, Flow Builder has become the standard automation tool for Salesforce Admins and Developers.
Side-by-Side Feature Comparison
| Feature | Workflow Rules | Process Builder | Flow Builder |
|---|---|---|---|
| Trigger: Record created | ✅ | ✅ | ✅ |
| Trigger: Record edited | ✅ | ✅ | ✅ |
| Trigger: Record deleted | ❌ | ❌ | ✅ |
| Trigger: Scheduled (time-based) | ⚠️ Time-delayed only | ⚠️ Scheduled actions only | ✅ Full schedule triggers |
| Trigger: Platform Event | ❌ | ❌ | ✅ |
| Update triggering record | ✅ | ✅ | ✅ |
| Update related records | ⚠️ Limited | ✅ | ✅ |
| Update any unrelated record | ❌ | ❌ | ✅ |
| Create records | ⚠️ Tasks only | ✅ | ✅ |
| Delete records | ❌ | ❌ | ✅ |
| Post to Chatter | ❌ | ✅ | ✅ |
| Send email alert | ✅ | ✅ | ✅ |
| Submit for approval | ❌ | ✅ | ✅ |
| Call Apex | ❌ | ✅ | ✅ |
| Launch a Flow | ❌ | ✅ | ✅ (Subflow) |
| Outbound messages | ✅ | ❌ | ✅ |
| Loops/iteration | ❌ | ❌ | ✅ |
| Screen flows (user UI) | ❌ | ❌ | ✅ |
| Error/fault handling | ❌ | ❌ | ✅ |
| Before-save execution | ❌ | ❌ | ✅ |
| Multiple criteria groups | ❌ | ✅ | ✅ |
| Ongoing Salesforce support | ❌ Retired | ❌ Retired | ✅ |
Real-World Examples: Which Tool Would You Have Used?
To better understand the differences among Workflow Rules, Process Builder, and Flow Builder, let’s look at some common business scenarios and see which tool was used in the past and which is recommended today.
Scenario 1: Send an Email When a Case Is Created
Business Requirement:
Whenever a new Case is created, automatically send an email notification to the customer or support team.
Workflow Rules
This was a perfect use case for Workflow Rules.
You could create a Workflow Rule on the Case object, set the criteria to run when a Case is created, and add an Email Alert action. The setup was simple and required only a few minutes.
Process Builder
Process Builder could also handle this requirement by triggering when a Case record is created and sending an Email Alert.
However, for such a simple automation, Process Builder was usually more than necessary.
Flow Builder (Recommended Today)
Today, the best approach is to use a Record-Triggered Flow.
A typical configuration would be:
- Object: Case
- Trigger: When a record is created
- Entry Conditions: Define criteria if needed, or run for all Cases
- Action: Send an Email Alert or Send Email action
Flow Builder provides the same functionality while keeping all automation within Salesforce’s recommended automation platform.
Scenario 2: When an Opportunity Is Closed Won, Update a Field on the Related Account
Business Requirement:
When an Opportunity is marked as Closed Won, automatically update a field on the related Account, such as Customer Status or Last Purchase Date.
Workflow Rules
Workflow Rules could handle this using a cross-object field update.
You could create a Workflow Rule on the Opportunity object and update a field on the related Account. However, the functionality was limited and inflexible as business logic became more complex.
Process Builder
Process Builder made this much easier.
You could set criteria such as Stage = Closed Won and use the Update Records action to update fields on the related Account.
Flow Builder (Recommended Today)
With Flow Builder, you can create a Record-Triggered Flow on the Opportunity object.
A typical approach would be:
- Trigger when the Opportunity is updated
- Check whether the Stage changes to Closed Won
- Use an Update Records element to update the related Account
Flow Builder provides a cleaner design and allows additional logic if future requirements become more complex.
Scenario 3: When an Opportunity Is Closed Won, Create a Follow-Up Task for Every Contact on the Account
Business Requirement:
After an Opportunity is won, create a separate follow-up Task for each Contact associated with the Account.
Workflow Rules
Workflow Rules could create a Task, but only a single Task based on the triggering record.
They could not retrieve related Contacts or automatically create multiple Tasks.
Process Builder
Process Builder could create records, but it could not loop through a collection of Contacts.
As a result, creating individual Tasks for every Contact was not possible without using Flow or Apex.
Flow Builder (Recommended Today)
Flow Builder can easily handle this requirement.
A typical solution would be:
- Trigger the Flow when the Opportunity becomes Closed Won.
- Use Get Records to retrieve all Contacts related to the Account.
- Use a Loop element to iterate through each Contact.
- Use Create Records to create a Task for every Contact.
This can be achieved entirely with clicks and no Apex code.
Scenario 4: Archive Cases Closed More Than 90 Days Ago Every Sunday
Business Requirement:
Run a weekly process to find Cases closed more than 90 days ago and mark them as Archived.
Workflow Rules
Workflow Rules supported time-based actions, but those actions were tied to individual records.
They could not run a scheduled job that scans all existing records every week.
Process Builder
Process Builder supported scheduled actions, but those actions were also tied to records that met specific criteria.
It was not designed for large-scale scheduled record processing.
Flow Builder (Recommended Today)
A Schedule-Triggered Flow is the ideal solution.
The Flow can:
- Run automatically every Sunday.
- Retrieve all Cases closed more than 90 days ago.
- Update the records and mark them as Archived.
No Apex code is required.
Scenario 5: Guide a Sales Rep Through a Step-by-Step Process
Business Requirement:
Provide a guided experience in which a sales representative enters call details, creates follow-up activities, and receives confirmation upon completion.
Workflow Rules
Workflow Rules run in the background and have no user interface. They cannot collect information from users or display screens.
Process Builder
Process Builder also runs in the background and cannot interact directly with users. It cannot display forms, collect input, or guide users through a process.
Flow Builder (Recommended Today)
This is a perfect use case for a Screen Flow.
A Screen Flow can:
- Display multiple screens
- Collect user input
- Validate entered data
- Create or update records
- Display confirmation messages
- Guide users through a structured business process
Screen Flows are widely used in Salesforce to replace custom Visualforce pages and provide user-friendly experiences without code.
These examples clearly show why Salesforce moved toward Flow Builder. While Workflow Rules and Process Builder were useful for basic automation, Flow Builder can handle simple tasks, complex business processes, scheduled automation, and interactive user experiences—all within a single automation platform.
Why Salesforce Retired Workflow Rules and Process Builder
One of the biggest reasons Salesforce moved away from Workflow Rules and Process Builder was the complexity and performance issues of automation.
In many Salesforce orgs, it was common to have multiple automation tools running on the same object. For example, an Opportunity object might have:
- Multiple Workflow Rules
- Several Process Builder processes
- One or more Flows
- Apex Triggers
Whenever an Opportunity record was created or updated, all these automations could execute. This made it difficult for admins and developers to understand exactly what was happening behind the scenes.
Troubleshooting became challenging because automation was spread across different places in Salesforce:
- Workflow Rules had their own configuration area
- Process Builder had a separate interface
- Flows were managed separately
- Apex Triggers were stored in code
As automation grew, finding the source of an issue often required checking multiple tools.
Another challenge was performance. Process Builder was powerful, but it consumed more system resources than an equivalent Flow.
In orgs with many active Process Builders, this could lead to slower automation execution and increased consumption of governor limits.
By moving automation to Flow Builder, Salesforce provided a single platform where admins and developers can build, manage, and troubleshoot automation more efficiently.
Some key benefits of Flow Builder include:
- Centralized automation management
- Better performance
- More advanced functionality
- Easier troubleshooting
- Continued Salesforce investment and feature enhancements
Because of these advantages, Salesforce made Flow Builder the future of automation.
What Should You Use Today?
For new Salesforce automation projects, the answer is simple:
Use Flow Builder.
Salesforce recommends using Flow Builder for all automation requirements, whether they are simple or complex.
If you are working in an older Salesforce org that still uses Workflow Rules or Process Builder, consider creating a plan to migrate those automations to Flow Builder.
Salesforce provides migration tools that can help convert many Workflow Rules and Process Builder automations into Flows. For more complex automations, rebuilding them manually in Flow is often the best approach.
Which Type of Flow Should You Use?
Here is a simple guide to help you choose the right Flow type.
Simple Field Updates Before a Record Is Saved
Use: Before-Save Record-Triggered Flow
Example:
- Update a status field
- Populate default values
- Calculate field values
This is one of the fastest automation options available in Salesforce.
Multiple Actions After a Record Is Saved
Use: After-Save Record-Triggered Flow
Example:
- Create related records
- Send email notifications
- Update related objects
- Trigger approval processes
Scheduled Automation
Use: Schedule-Triggered Flow
Example:
- Archive old records
- Send weekly reminders
- Perform regular data cleanup
User-Guided Processes
Use: Screen Flow
Example:
- Data entry wizards
- Employee onboarding forms
- Guided sales processes
Event-Based Automation
Use: Platform Event-Triggered Flow
Example:
- Respond to events from external systems
- Process integration messages
Reusable Automation Logic
Use: Autolaunched Flow
Example:
- Common logic used across multiple Flows
- Shared business processes
Workflow Rules vs Process Builder vs Flow Builder: Final Verdict
Workflow Rules
Workflow Rules were excellent for simple automation.
They were easy to configure, reliable, and worked well for tasks such as:
- Sending email alerts
- Updating fields
- Creating tasks
- Sending outbound messages
However, they were limited and could not support the more advanced automation needs of modern Salesforce organizations.
Process Builder
Process Builder was a major improvement over Workflow Rules.
It allowed admins to create more sophisticated automation without writing Apex code and became one of the most popular Salesforce automation tools for many years.
However, it had several limitations:
- No support for loops
- No record-delete triggers
- No screen-based user interaction
- Limited error handling
- Performance challenges in heavily automated orgs
Flow Builder
Flow Builder combines the capabilities of Workflow Rules and Process Builder while adding many advanced features.
With Flow Builder, you can:
- Build simple and complex automation
- Create interactive user experiences
- Run scheduled processes
- Process large collections of records
- Handle errors gracefully
- Integrate with external systems
Although Flow Builder has a learning curve, it provides the flexibility and power needed for modern Salesforce automation.
Frequently Asked Questions
Are Workflow Rules and Process Builder completely gone from Salesforce?
They still exist in most orgs, but Salesforce ended all support on December 31, 2025. You can’t create new ones. Existing automations may still run, but without bug fixes or Salesforce support.
Which was better — Workflow Rules or Process Builder?
Process Builder was more capable in almost every way. The only real advantage of Workflow Rules was simplicity — for a single-field update or email alert, they were faster to set up. But for anything more complex, Process Builder was the better choice. Both are now replaced by Flow Builder.
Can Flow Builder do everything that Workflow Rules and Process Builder could do?
Yes. Everything both tools could do, Flow Builder can do — and significantly more. The only minor nuance is outbound messages, which Workflow Rules support natively. In Flow Builder, you can achieve the same result using a custom callout or an external action.
Is there a way to see all automation in a Salesforce org in one place?
Yes. Go to Setup → Automation Lightning App (or search “Automation” in Quick Find). This gives you a consolidated view of all active flows. For a complete picture, including any remaining Workflow Rules and Process Builder processes, you’ll also need to check those lists separately in Setup.
Will my old Workflow Rules and Process Builder automations just stop working one day?
Salesforce hasn’t set a hard end-of-execution date yet. Existing automations may continue to run even without support. But “may continue to run without guarantee” is not a place you want your production automation to be. The risk isn’t worth it — migrate to Flow.
Final Thoughts
Workflow Rules and Process Builder played an important role in Salesforce automation for many years. They helped admins automate business processes without writing code and paved the way for more advanced automation tools.
Today, Flow Builder is the standard automation platform in Salesforce. It is actively maintained, continuously enhanced, and capable of handling almost every automation requirement.
If you are investing time in learning Salesforce automation, Flow Builder is the tool that deserves your focus.
You may like to read:
- Create & Send HTML Emails Using Rich Text Template in Salesforce Flow
- Avoid Validation Rules Using Salesforce Flow
- Automatically Delete Records Using Salesforce Flows
- How to Use Email Templates Directly in Salesforce Flow (Release Update)
I am Bijay Kumar, the founder of SalesforceFAQs.com. Having over 10 years of experience working in salesforce technologies for clients across the world (Canada, Australia, United States, United Kingdom, New Zealand, etc.). I am a certified salesforce administrator and expert with experience in developing salesforce applications and projects. My goal is to make it easy for people to learn and use salesforce technologies by providing simple and easy-to-understand solutions. Check out the complete profile on About us.
