TutorialKart.comProcess Builder Salesforce is a legacy point-and-click automation tool that was used to run actions when records met defined criteria. It helped admins automate record updates, email alerts, task creation, approval submissions, and other business actions without writing Apex code. In current Salesforce implementations, new automation should be built in Flow Builder, while Process Builder is mainly relevant for understanding and maintaining older orgs.
Salesforce has ended support for Workflow Rules and Process Builder as of December 31, 2025, and Salesforce guidance is to migrate existing automation to Flow Builder. You may still see existing processes in older Salesforce orgs, so admins and developers should understand how Process Builder works before reviewing, troubleshooting, or migrating those automations.
What is Process Builder Salesforce?
Process Builder in Salesforce is a declarative automation tool that evaluates records against criteria and then performs actions when the criteria are true. A process is built around an object, a trigger condition, one or more criteria nodes, and immediate or scheduled actions.
For a new Salesforce automation design, use Flow Builder. For older automations, use Process Builder knowledge to identify what the process does, whether it still runs, and how it should be rebuilt as a record-triggered flow or another suitable flow type.
How Process Builder Automation Runs on Salesforce Records
A Process Builder automation normally follows a simple pattern: select the object, define when the process starts, add criteria, and configure the actions. When a record change satisfies the criteria, Salesforce runs the actions in the process. If the criteria are not met, Salesforce moves to the next criteria node or stops the process, depending on the configuration.
| Process Builder part | Purpose in Salesforce automation |
|---|---|
| Object | The Salesforce object on which the process is based, such as Account, Opportunity, Case, or a custom object. |
| Start condition | Defines when the process begins, such as when a record is created or edited. |
| Criteria node | Checks whether the record meets specific conditions. |
| Immediate actions | Actions that run as soon as the criteria are met. |
| Scheduled actions | Actions that are scheduled to run later, based on a date or time value. |
Common Process Builder Actions in Salesforce
Process Builder was commonly used when a business rule needed more than a basic workflow rule but did not require custom Apex. Typical actions included record updates, creating related records, launching flows, submitting records for approval, and calling Apex where declarative actions were not enough.
- Create a new record, such as a follow-up Task when an Opportunity stage changes.
- Update the same record or a related record when defined criteria are met.
- Send an email alert by using an existing email alert configuration.
- Post to Chatter for a record-related notification.
- Submit a record for approval when it reaches a qualifying status.
- Launch another flow or call Apex for more advanced automation logic.
Process Builder Salesforce Example for Opportunity Follow-Up
Assume the sales team wants a follow-up task whenever an Opportunity is moved to the Proposal stage. In Process Builder, the automation can be designed like this:
| Configuration item | Example value |
|---|---|
| Object | Opportunity |
| Start condition | When a record is created or edited |
| Criteria | Opportunity Stage equals Proposal |
| Immediate action | Create a Task for the Opportunity owner |
| Task details | Subject: Follow up on proposal; Due Date: 3 days from today |
This example shows why Process Builder was useful: the admin could configure a business action without writing code. In a current Salesforce org, the same requirement should normally be built as a record-triggered flow.
What is Workflow in Salesforce?
- Workflows are fast, easy and button-click friendly.
- Workflow rules will be triggered based on a set of criteria.
Workflow Rules are also legacy automation. They are simpler than Process Builder and were mainly used for field updates, email alerts, tasks, and outbound messages. Salesforce recommends Flow Builder for new automation instead of Workflow Rules or Process Builder.
What is Visual Workflow in Salesforce?
Visual Workflow is the older name associated with Salesforce flows. Screen flows are run by users and can display screens for collecting or showing information. Modern Flow Builder also supports automations that run without a screen, including record-triggered flows, scheduled flows, and autolaunched flows.
- Flows are not limited to one simple workflow rule.
- They can look up, create, update, and delete records for multiple objects.
In current Salesforce usage, Flow Builder is the main automation builder. It supports automation patterns that go beyond the older Workflow Rules and Process Builder model.
Workflow Rules vs Process Builder vs Flow Builder in Salesforce
The most important difference is that Workflow Rules and Process Builder are legacy tools, while Flow Builder is the recommended tool for new Salesforce automation. The comparison below helps when reviewing older automation or planning a migration.
| Feature | Workflow Rules | Process Builder | Flow Builder |
|---|---|---|---|
| Current role | Legacy automation | Legacy automation | Recommended automation tool |
| Typical use | Simple field updates, tasks, email alerts, outbound messages | Multi-step record automation with criteria and actions | Simple to advanced automation across many use cases |
| Interface | Rule-based setup pages | Visual process canvas | Visual flow canvas |
| Record delete support | No | No | Supported in suitable flow designs |
| Best choice for new automation | No | No | Yes |
Is Process Builder Still Used in Salesforce?
Process Builder may still exist in older Salesforce orgs because many businesses created automations with it before Flow Builder became the preferred option. However, it should be treated as a legacy tool. Salesforce has blocked new process creation in most production orgs, and Salesforce documentation recommends moving processes and workflow rules to Flow Builder with the Migrate to Flow tool where possible.
Before changing an existing process, review what triggers it, which criteria nodes are active, which actions run, and whether another automation also updates the same records. This review helps avoid duplicate updates, recursion, or changed behavior during migration.
When to Migrate Process Builder to Flow Builder
Migration is usually appropriate when the process is still active, supports an important business rule, or causes maintenance problems. A direct one-to-one migration is not always the best design. Review the automation first, then decide whether it should become one record-triggered flow, a scheduled flow, an autolaunched flow, or part of a broader automation redesign.
- Migrate active processes that still run business-critical automation.
- Combine related processes when they update the same object and can be safely managed in one flow.
- Replace old scheduled actions with scheduled paths or another suitable Flow design.
- Test migrated flows with bulk records, not only with one manual record update.
- Deactivate legacy processes only after confirming that the replacement flow produces the expected result.
Process Builder Salesforce FAQ
What is Process Builder in Salesforce with an example?
Process Builder in Salesforce is a legacy automation tool that runs actions when record criteria are met. For example, when an Opportunity stage changes to Proposal, a process can create a follow-up Task for the Opportunity owner.
What does Process Builder do in Salesforce?
Process Builder evaluates record changes and runs configured actions such as creating records, updating related records, sending email alerts, posting to Chatter, launching flows, submitting approvals, or calling Apex.
What is the difference between Workflow and Process Builder in Salesforce?
Workflow Rules handle simpler automation such as field updates and email alerts. Process Builder supports more complex, multi-step criteria and actions on a visual canvas. Both are legacy tools, and Salesforce recommends Flow Builder for new automation.
Is Process Builder still used in Salesforce?
Process Builder is still found in older orgs, but it is no longer the preferred tool. Salesforce has ended support for Workflow Rules and Process Builder and recommends migrating automation to Flow Builder.
Should I create new automation in Process Builder or Flow Builder?
Create new automation in Flow Builder. Process Builder should mainly be used for understanding, maintaining, or migrating older automations that already exist in a Salesforce org.
Editorial QA Checklist for Process Builder Salesforce Tutorial
- Confirm that the tutorial clearly says Process Builder is a legacy Salesforce automation tool.
- Verify that new Salesforce automation is directed to Flow Builder, not Process Builder.
- Check that Workflow Rules, Process Builder, and Flow Builder are compared without mixing their capabilities.
- Ensure the Process Builder example uses a realistic Salesforce record-change automation.
- Confirm that the existing Process Builder image and internal Workflow links are retained without changing their URLs.
Process Builder Salesforce was introduced as a more flexible alternative to workflow rules for common record-based automation. Process builder in Salesforce allows user to:
Process Builder salesforce and older Visual Workflow tools allowed users to create customized processes and guided experiences. Both tools offered a selection of actions that could be performed based on criteria defined by the user. Available actions could also be extended by packages installed in the org. This gave admins another way to build automation scenarios without writing code.