Process Builder is Salesforce’s previous-generation visual automation tool — point-and-click record-change automation with branching, time-based actions, and a wider set of triggers than Workflow Rules. As of Winter ‘23, you can no longer create new Process Builder processes in fresh orgs, and the recommendation is to migrate to Flow.
Why it existed
Process Builder filled the gap between Workflow Rules (one-shot field updates, limited triggers) and Apex (full code). It introduced:
- Branching logic — multiple criteria sets in one process
- Multi-step actions — chain a field update, an email, a record creation
- Record creation — could create child records (Workflow couldn’t)
- Platform Event subscription — react to events without code
- Submit for Approval as an action
For a few years, Process Builder was the default declarative tool — until Flow caught up and overtook it on every dimension.
What it does
- Triggers on record change (insert or update), platform event, or invocable subprocess
- Evaluates criteria sets (top-to-bottom)
- For each matched criteria, runs immediate actions and/or scheduled actions
- Can call Apex, flows, or subprocesses
The action types
| Type | What it does |
|---|---|
| Create a Record | Insert a new record on any object |
| Update Records | Update the triggering record OR related records |
| Email Alerts | Send a templated email |
| Quick Actions | Invoke a configured Quick Action |
| Post to Chatter | Create a Chatter post |
| Submit for Approval | Auto-submit |
| Launch a Flow | Call an autolaunched flow |
| Call Apex | Invocable Apex method |
Why it’s being retired
Maintaining four automation tools (Workflow, Process Builder, Approval Process, Flow) wasn’t sustainable. Salesforce consolidated on Flow and is investing exclusively there. Process Builder’s UI was clunky for complex processes, debug experience was poor, and bulkification was opaque — Flow fixes all of these.
What “retired” means in 2026
- Existing Process Builder processes continue to run — Salesforce hasn’t pulled the rug
- You can’t create new processes in orgs created after Winter ‘23
- You can’t add new actions to existing processes in many cases
- You should migrate using the Migrate to Flow tool in Setup
What interviewers want
- A clear definition: legacy visual automation, replaced by Flow
- Awareness that new Process Builder processes can’t be created in fresh orgs
- That Flow is the modern replacement, with the Migrate to Flow path
Related
- How is Process Builder different from Workflow?
- What is a Flow?
Verified against: Salesforce Help — Process Builder and Migrate to Flow. Last reviewed 2026-05-17 for Spring ‘26 release.