- Home
- Salesforce integration
- Salesforce automation
Salesforce automation runs on Flow, Apex and agents; each save runs flows in a set order
Salesforce automation lets the system do routine steps for you. The work runs on Flow, Salesforce's built-in automation tool, on Apex code and on AI agents. We read Salesforce's own guides, version 68.0, on 18 November 2026 for the flow types, their order and the email limits.
What Salesforce automation does
Salesforce automation hands routine steps to the system. Salesforce’s own words: it is “using technology to perform often tedious human tasks”. The aim is less manual time, effort and error.
It sits on top of the CRM, the customer records. Salesforce says CRM tools manage customer data and track deals through the sales process. Sales engagement platforms then guide outreach and, in some cases, automate it.
Three engines do the work inside Salesforce today:
Scroll the table sideways to see every column.
| Engine | What it is | Suits |
|---|---|---|
| Flow | Automations Salesforce runs on record changes, schedules, events or user screens | Record updates, scheduled jobs, screens for users, approvals |
| Apex | Code a Salesforce customer writes, including triggers on record saves | Logic a flow cannot express, within strict per-transaction limits |
| AI agents | Agentforce agents, or custom agents that work through Salesforce’s API | Jobs that need reading and judgment, such as an emailed request |
Older tools still run too. Workflow rules and Process Builder processes keep firing on each save, as the order below shows. Salesforce’s Help pages on retiring them did not load for our fetcher, so this page gives no date for that.
Flow types, and what starts each one
A flow’s trigger decides when it runs. Salesforce’s Metadata API lists these triggers, among others:
Scroll the table sideways to see every column.
| Trigger | When the flow runs |
|---|---|
| RecordBeforeSave | When a record is created or updated, to change that record before it is saved |
| RecordAfterSave | After a record is saved |
| RecordBeforeDelete | Before a record is deleted |
| Scheduled | At the scheduled time |
| PlatformEvent | When a platform event message arrives |
| ExternalSystemChange | When a change is detected in an outside system, from API version 63.0 |
A flow with no trigger starts only when a user or an app launches it. The Metadata API also sorts flows by kind:
- Screen flow. Needs a person, because it has screens, local actions or choices.
- Autolaunched flow. Needs no user at all.
- Orchestration. Groups flows into steps, inside a series of stages.
- Approval workflow. An orchestration that runs an approval, from API version 63.0.
ExternalSystemChange is worth a look for integration work. A flow can start from a change in another system, not only from a Salesforce record.
The order Salesforce runs automation on each save
One record save can fire several automations, and Salesforce runs them in a fixed order. Its Apex Developer Guide lists the steps. These are the main ones:
- Record-triggered flows set to run before the save.
- Before triggers, which are Apex code.
- After triggers, once the record is saved but not yet committed.
- Rules that assign the record, then rules that send auto-replies.
- Workflow rules, at step 11 of Salesforce’s list.
- Escalation rules.
- Process Builder processes, in an order Salesforce does not fix.
- Record-triggered flows set to run after the save.
- Work after the commit, such as sending email.
Three facts follow from that list. First, Salesforce says to use record-triggered flows if you need to control the order of Flow automations. Second, emails go out only after the commit, so a save that fails before then sends no email. Third, Salesforce warns not to edit the metadata of retrieved Process Builder processes. So change a process in Salesforce, or replace it with a record-triggered flow, rather than editing its metadata.
Automated emails in Salesforce have daily limits
When an org reaches the daily limit, the newly counted emails cannot be sent. Salesforce then emails you and adds an entry to the debug logs. These are the limits, from its Apex guide:
Scroll the table sideways to see every column.
| Limit | What Salesforce says |
|---|---|
| Single email, per day | Up to 5,000 external email addresses per licensed org, counted in GMT |
| What counts, in orgs from Spring ’19 on | Email alerts, simple email actions, Send Email actions in flows and REST API, as well as Apex |
| What counts, in orgs created before Spring ’19 | Only emails sent through Apex and Salesforce APIs, not REST API |
| Not counted | Single emails sent from the email author or composer in Salesforce |
| Mass and list email, per day | Up to 5,000 external addresses per licensed org |
| Single email in Developer Edition and trial orgs | 50 recipients a day, and up to 15 per email |
| Mass and list email in Developer Edition and trial orgs | No more than 10 external recipients per org a day |
| Recipients on one email | Up to 150 across To, CC and BCC |
| Apex sendEmail calls | 10 per transaction |
Two rules change the count. Duplicate addresses count each time they appear. And in Apex, an email to your own users sent by user ID through setTargetObjectId does not count. The same email sent to their email addresses does count.
So a busy flow with an email alert can use up the daily cap. A send that must reach a customer, such as a quote, counts against it, so plan for the cap or create a task for the rep.
Apex limits bound the code behind automation
Apex code runs under per-transaction limits. These come from the same guide:
Scroll the table sideways to see every column.
| Limit | Synchronous | Asynchronous |
|---|---|---|
| SOQL queries per transaction | 100 | 200 |
| sendEmail calls per transaction | 10 | 10 |
Scheduled Apex is a background job, yet Salesforce says the synchronous limits apply to it. So a nightly job gets 100 queries per transaction, not 200.
The automated case user is the name rules leave in case history
The automated case user is the name in a case’s history when a rule changed the case. Salesforce calls it the default case user. It covers four kinds of change: assignment rules, escalation rules, On-Demand Email-to-Case and cases logged in the Self-Service portal.
A separate setting can make the system user play that role. Pick a user your service team will recognize in the history, so nobody chases a person who never touched the case.
Where AI agents fit in Salesforce automation
A flow follows fixed rules. An agent reads a request and drafts a reply. They work together. Salesforce says Agentforce Builder connects agents to Flows, Apex, MuleSoft APIs and prompt templates, and that Flows can create automations across any system.
Our team has built Salesforce agents for six jobs, some in Agentforce and some as custom agents. Two of them are automation jobs:
- Lead qualification. The agent checks each new lead against your rules, such as company size, industry, region or the product asked about. It sets the lead’s status and routes the good ones to a rep.
- Follow-up cadence. The agent watches each open lead or deal. When a step is due, it drafts the email or creates the call task for the rep, and it stops when the buyer replies.
Our team also takes Salesforce implementation end to end: the org set up, the data moved in and the team trained. See Salesforce AI agents for all six jobs.
Quote and RFQ automation in Salesforce
Salesforce CPQ is end of sale, not end of life: existing customers keep it, but new customers cannot buy it. Salesforce says Revenue Cloud with Agentforce can generate, update and send a quote. Its Place Sales Transaction API takes up to 1,000 quote lines per quote.
Salesforce quotes and RFQs shows what replaced CPQ. It lists the quote records and APIs an agent uses, and how an emailed RFQ gets in.
Report and dashboard automation in Salesforce
Reports can go out on a schedule and download as Excel, and dashboards refresh by API. Salesforce caps dashboard refreshes at 200 an hour for the org, and the reports API returns the first 2,000 rows per run.
Salesforce reports and dashboards shows how the two differ. It lists the three dashboard types and each hourly limit.
AI assistants and Salesforce, through MCP
MCP is an open standard that lets an AI assistant call another system’s tools. Salesforce’s local DX MCP Server reached end of life on 2 November 2026. Salesforce MCP settles which Salesforce MCP servers still work and how each signs in.
For links between Salesforce and your ERP or other systems, start with Salesforce integration. The first call is free.
Questions
What does Salesforce automation do?
It takes routine steps off people. Salesforce defines sales automation as using technology to do tedious human tasks, cutting manual time, effort and error. In practice, a flow updates a record when it changes, a scheduled flow runs at a set time, an email alert goes out, and an agent qualifies a lead. A person still approves what matters, such as a quote.
What is the difference between a CRM and sales force automation?
A CRM holds the records, and automation acts on them. Salesforce says CRM tools manage customer data and track deals through the sales process. It says sales engagement platforms guide outreach and, in some cases, automate it. Salesforce puts both in one place, with the records in Sales Cloud and the automation in Flow, Apex and Agentforce on top.
What is the best tool for Salesforce automation?
It depends on the job, and Salesforce's own guides point the way. Use a record-triggered flow for record changes, because Salesforce says that is how to control the order of automation. Use Apex code for logic a flow cannot express, within its per-transaction limits. Use an agent for jobs that need reading and judgment, such as an emailed request.
Why do automated emails stop sending in Salesforce?
Check the daily limit first. Salesforce lets each licensed org send single emails to at most 5,000 external addresses a day, counted in GMT. For orgs created in Spring '19 or later, that count includes email alerts, simple email actions, Send Email actions in flows and REST API sends. When a newly counted email cannot be sent, Salesforce emails you and adds a debug log entry.
What is the automated case user in Salesforce?
It is the name Salesforce shows in a case's history when a rule changed the case. Salesforce calls it the default case user. It covers changes from assignment rules, escalation rules, On-Demand Email-to-Case and cases logged in the Self-Service portal. A separate setting can make the system user play that role. Pick a name your team will know.
Do we need an official Salesforce partner to do this?
Not for this work. What decides an automation or an agent is a team that knows Salesforce from the inside and builds on Salesforce's published APIs. Our team takes Salesforce implementation end to end and has built Salesforce agents for six jobs, in Agentforce and as custom agents. You license Salesforce from Salesforce or its reseller, and we take the build from there.
Sources
Every source behind a figure or a vendor fact on this page, with the day we read it.
- Salesforce, Apex Developer Guide, version 68.0 (PDF)Read 18 Nov 2026
- Salesforce, Metadata API Developer Guide (PDF)Read 18 Nov 2026
- Salesforce, Sales CloudRead 18 Nov 2026
- Salesforce, Agentforce BuilderRead 18 Nov 2026
- Salesforce, AgentforceRead 18 Nov 2026
- Salesforce, Revenue Cloud overviewRead 18 Nov 2026
- Salesforce, Salesforce CPQ end of sale articleRead 18 Nov 2026
- Salesforce, Revenue Management Developer Guide (PDF)Read 18 Nov 2026
- Salesforce, Reports and Dashboards REST API Developer Guide (PDF)Read 18 Nov 2026
- Salesforce on GitHub, DX MCP Server end of life noticeRead 18 Nov 2026
- CadenceWorks, Salesforce AI agentsRead 18 Nov 2026
Pages in this section
- Salesforce quotes and RFQsSalesforce no longer sells CPQ to new customers, and Revenue Cloud Advanced replaces it. The quote records, APIs and limits, and where an RFQ agent fits.
- Salesforce reports and dashboardsHow to automate Salesforce reports and dashboards: report formats, dashboard types, hourly API limits, subscriptions, Excel export and Tableau Next.
Bring your Salesforce automation list to a first call
The first call is free. Bring the flows, workflow rules and automated emails you run today, and the steps your team still does by hand, and we can talk through what to move first.