Salesforce automation is the use of Salesforce's built-in tools to carry out business steps without manual work: routing leads and cases, updating records, sending emails, creating tasks and calling other systems. In 2026 the toolkit is Flow for most jobs, assignment and escalation rules for routing, approvals, Apex for heavy logic, and Agentforce agents for work that needs judgement.
This post was first published in 2021 as "10 ideas to achieve automation with Salesforce CRM". It has been rewritten for 2026: Workflow Rules and Process Builder are out of support, Flow does most of the work, and AI agents are a new layer.
Salesforce automation or sales force automation?
The same search covers two things: automating work inside the Salesforce platform, which is what this guide is about, and "sales force automation" (SFA), the software category for automating a sales team's routine work. Salesforce's own sales automation guide defines it as using technology to perform often tedious human tasks, and lists contact management, prospecting and lead scoring, opportunity management, conversation analysis, territory management, forecasting and quote configuration. In Salesforce, those SFA jobs are delivered by Sales Cloud features and the tools below.
What can you automate in Salesforce?
You can automate almost any step that follows a rule. The common categories are:
- Record updates: set fields, stamp dates, keep related records in sync.
- Routing: give each lead or case the right owner or queue.
- Communication: confirmation emails, internal alerts, reminders.
- Tasks and follow-ups: create the next step when a stage changes.
- Approvals: discounts, expenses, contracts.
- Integration: send or fetch data from ERP, billing or support systems.
- Guided work: screens that walk users through a process.
- Judgement calls: answering customers or qualifying leads, now handled by AI agents within guardrails.
The Salesforce automation tools in 2026
As of November 2026, Flow is the main Salesforce automation tool, alongside assignment, auto-response and escalation rules, approvals, Apex and Agentforce agents. Workflow Rules and Process Builder are past end of support.
| Tool | What it does | Status |
|---|---|---|
| Flow (Flow Builder) | Record-triggered, schedule-triggered, platform event-triggered, screen and autolaunched flows, plus flows triggered by Data 360 changes | The main tool for new automation |
| Assignment rules | Assign leads and cases to users or queues; entries are checked in order and the first match wins | Current |
| Auto-response rules | Send an email reply to new leads or cases based on their fields; one active rule each for leads and cases | Current |
| Escalation rules | Reassign or notify when a case stays open too long, within business hours | Current |
| Approvals | Route records for sign-off; classic approval processes and newer Flow approval processes | Current |
| Apex triggers and classes | Code for complex, high-volume or transactional logic | Current |
| Agentforce agents | AI agents that choose and run actions (flows, Apex, APIs, prompt templates) within guardrails | Current |
| Workflow Rules and Process Builder | Older declarative tools | Support ended 31 Dec 2025; replaced by Flow |
Flow types are from Trailhead's Flow Basics. Lead and case routing behaviour is from Salesforce Help on assignment rules and escalation rules, which allow up to five escalation actions per rule entry, and on auto-response rules, where only one lead rule and one case rule can be active at a time. Salesforce's end-of-support notice confirms that existing Workflow Rules and processes keep running after 31 December 2025, but get no support or bug fixes. Our Workflow Rules guide covers the migration.
How do you choose the right Salesforce automation tool?
Pick the simplest tool that does the job: Flow for most record automation, rules for routing, Apex for volume and complexity, and an agent only where judgement is needed. Salesforce's record-triggered automation decision guide gives clear rules. In short:
- Changing fields on the same record? Use a before-save record-triggered flow. It avoids an extra save and is the fastest declarative option.
- Updating related records, sending alerts, or acting later? Use an after-save flow; scheduled paths handle "three days before the renewal date" logic and replace time-based workflow.
- Routing a lead or case? Use assignment rules first; they are simple and admins can maintain them. Use Flow when routing needs data the rules can't see.
- High volumes, complex logic, or a need for rollbacks? Use Apex, or a hybrid where Flow calls invocable Apex.
- Keep one entry point per object. The guide warns against mixing flows and Apex triggers on the same object, because the order becomes hard to predict. Our order of execution guide shows why.
- Does the step need judgement, such as reading a customer's message? That is where an Agentforce agent fits, calling your existing flows as its actions.
10 processes worth automating in Salesforce
The best first candidates are frequent, rule-based steps in sales and service: lead routing, follow-ups, approvals, escalations, renewals and data sync.
| # | Process | Typical tool |
|---|---|---|
| 1 | Assign new leads by region, product or round robin | Lead assignment rules, or Flow for round robin |
| 2 | Send a confirmation email when a web lead or case arrives | Auto-response rules |
| 3 | Create follow-up tasks when an opportunity changes stage | After-save record-triggered flow |
| 4 | Stamp dates and keep status fields consistent, such as lead status changes | Before-save record-triggered flow |
| 5 | Route discounts above a threshold for approval | Approval process |
| 6 | Escalate cases that breach response times | Escalation rules |
| 7 | Remind owners about renewals before the contract end date | Scheduled path on a record-triggered flow |
| 8 | Clean up stale records every week | Schedule-triggered flow |
| 9 | Sync closed-won orders to ERP or billing | Flow publishing a platform event, an integration tool, or Apex for volume (see integration patterns) |
| 10 | Answer common customer questions and hand over the rest | Agentforce Service Agent calling flows |
Start with the processes that are frequent, rule-based and annoying for people to do by hand. Those give the quickest return and the fewest surprises.
Where do AI agents fit in Salesforce automation?
Classic automation runs the same steps every time. Agentforce adds a layer that decides which steps to run. According to Salesforce's how Agentforce works page, agents reuse platform tools such as flows and Apex, and turn APIs and prompt templates into agent actions, all within guardrails. That makes good flows more valuable, not less: an agent is only as reliable as the actions it can call. Our Salesforce flows guide covers making flows agent-ready, and our Agentforce page shows typical agents.
Salesforce automation pitfalls
Most automation problems come from overlapping automations, untested bulk behaviour and missing error handling, not from the tools themselves.
- Too many automations on one object. Several flows, a trigger and old workflow rules on Opportunity make behaviour hard to predict. Consolidate.
- No bulk testing. Automation that works for one record can fail on a data load of 10,000. Test with volume and check governor limits.
- Automating a broken process. Fix the process first; automation only makes a bad one faster.
- No error handling. Add fault paths to flows and tell someone when a step fails.
- Leaving retired tools in place forever. Workflow Rules and Process Builder still run, but nobody will fix them if they break.
- Automating across systems without a plan. For automation that spans Salesforce and other apps, compare integration platforms first; see Workato vs MuleSoft and Workato vs Zapier.
- Using automation where a rule belongs. If you just need to stop bad data, a validation rule is simpler than a flow.
Getting help
Techila is a Salesforce Summit Partner. Our Salesforce consulting team audits existing automation, migrates Workflow Rules and Process Builder to Flow, and designs automation that scales, including the flows Agentforce agents rely on. Talk to us about the processes you want to automate first.
Frequently asked questions
What is Salesforce automation?
It is the use of Salesforce's built-in tools, mainly Flow, assignment and escalation rules, approvals, Apex and Agentforce agents, to carry out business steps without someone doing them by hand: routing records, updating fields, sending emails, creating tasks and calling other systems.
What is the main automation tool in Salesforce?
Flow. Record-triggered, scheduled, screen, autolaunched and platform event-triggered flows cover most automation, and Salesforce's architecture guidance treats record-triggered flow and Apex triggers as the two pillars of record automation.
Can I still use Workflow Rules and Process Builder?
Existing ones keep running, but Salesforce ended support for both on 31 December 2025: no customer support and no bug fixes. Build new automation in Flow and plan to migrate the old rules.
When should I use Apex instead of Flow?
Salesforce's record-triggered decision guide points to Apex for high-volume or high-density objects, complex logic, savepoints and rollbacks, and the after-undelete event, which flows do not support. A hybrid, Flow calling invocable Apex, suits medium complexity.
Is Agentforce a replacement for Flow?
No. Agentforce agents decide which action to take, and those actions are usually flows, Apex, APIs or prompt templates. Flow stays the way to run fixed steps; agents add judgement on top.