Process Builder (Legacy)
Learning Content
Last updated: July 21, 2026
Process Builder (Legacy)
Process Builder is a declarative automation tool that Salesforce introduced to overcome many of the limitations of Workflow Rules. It enables administrators to automate business processes using a visual interface without writing Apex code.
Although Process Builder is still supported for existing implementations, Salesforce recommends using Record-Triggered Flows for all new automation because they provide greater flexibility, better performance, and a broader range of capabilities.
💡 LearnFrenzy Insight
Imagine upgrading from a basic calculator to a spreadsheet.
A calculator performs one calculation at a time, while a spreadsheet can perform multiple calculations, make decisions, and automate complex workflows.
Workflow Rules are like the calculator. Process Builder is like the spreadsheet. Record-Triggered Flow is the modern automation platform that combines visual design with enterprise-level capabilities.
Where Does Process Builder Execute?
Database Save
│
▼
After Trigger
│
▼
Assignment Rules
│
▼
Auto-Response Rules
│
▼
Escalation Rules
│
▼
Workflow Rules
│
▼
⭐ Process Builder
│
▼
Record-Triggered Flow
│
▼
Roll-Up Summary
│
▼
Commit Transaction
Process Builder executes after Workflow Rules as part of Salesforce's declarative automation layer. Like Workflow Rules, it can update records and perform actions that may result in additional automation or save cycles, depending on the configuration.
What Can Process Builder Do?
| Capability | Description |
|---|---|
| Create Records | Create related Salesforce records automatically. |
| Update Records | Update the current record or related records. |
| Invoke Flows | Launch an autolaunched Flow. |
| Submit for Approval | Automatically start an approval process. |
| Call Apex | Invoke Apex methods marked with @InvocableMethod. |
| Post to Chatter | Create Chatter posts automatically. |
| Send Email Alerts | Notify users based on business conditions. |
Real Business Scenario
🏢 Business Example
Whenever an Opportunity reaches the Closed Won stage:
- Create a custom Project record.
- Update the related Account.
- Start an Approval Process.
- Invoke an Apex class to integrate with an ERP system.
- Notify the implementation team.
Historically, many Salesforce implementations used Process Builder to orchestrate this type of multi-step automation.
Workflow Rule vs Process Builder vs Record-Triggered Flow
| Feature | Workflow Rule | Process Builder | Record-Triggered Flow |
|---|---|---|---|
| Status | Legacy | Legacy | Recommended |
| Create Records | No | Yes | Yes |
| Update Related Records | Limited | Yes | Yes |
| Decision Logic | Basic | Moderate | Advanced |
| Loops | No | No | Yes |
| Call Apex | No | Yes | Yes |
| Future Investment | Maintenance Only | Maintenance Only | Strategic Platform |
When Should You Use Process Builder?
| Use Process Builder | Prefer Record-Triggered Flow |
|---|---|
| Maintaining existing automation. | Building new automation. |
| Supporting legacy implementations. | Complex business processes. |
| Minor updates to existing processes. | Enterprise-scale automation. |
| Migration planning. | Long-term Salesforce development. |
🔍 Behind the Scenes: What Happens Internally?
Workflow Rules Complete
│
▼
Process Builder Evaluated
│
▼
Criteria Met?
Yes │ No
│
▼
Execute Process Actions
│
▼
Update Records / Call Apex
│
▼
May Trigger Additional Automation
│
▼
Continue Order of Execution
Because Process Builder can update records and invoke other automation, developers must carefully design processes to avoid recursion, duplicate execution, and unnecessary complexity.
Why Understanding Process Builder Still Matters
| Reason | Explanation |
|---|---|
| Legacy Salesforce Orgs | Many production environments still contain Process Builders. |
| Migration Projects | Organizations frequently migrate Process Builder automation to Flow. |
| Interview Preparation | Common questions compare Workflow, Process Builder, and Flow. |
| Maintenance Work | Developers often need to troubleshoot or enhance existing processes. |
✅ Best Practice
Do not create new Process Builders unless there is a compelling reason to extend an existing legacy solution. For new implementations, use Record-Triggered Flows because they provide better performance, richer capabilities, and are Salesforce's strategic automation platform.
⚠️ Common Mistake
Using Process Builder and Record-Triggered Flow to automate the same business process without understanding the execution sequence. This can lead to duplicate updates, recursion, and difficult-to-debug automation.
Question: Why does Salesforce recommend Record-Triggered Flow instead of Process Builder for new automation?
Answer: Record-Triggered Flows support more complex logic, loops, subflows, richer decision-making, better debugging tools, and broader automation capabilities. Salesforce continues to invest in Flow as the strategic automation platform, while Process Builder is maintained primarily for existing implementations.
- ✔ Visual declarative automation tool.
- ✔ More powerful than Workflow Rules.
- ✔ Can create records, update related records, invoke Apex, and launch Flows.
- ✔ Still supported for existing implementations.
- ✔ Salesforce recommends Record-Triggered Flow for new automation.
- ✔ Frequently encountered during migration and maintenance projects.
➡ Next Lesson
In the next lesson, you'll learn about Record-Triggered Flows, Salesforce's modern declarative automation framework, and why it has become the recommended replacement for Workflow Rules and Process Builder.
Practice What You've Learned
Test your understanding with these practice exercises