Overview
Automation covers how administrators make Salesforce act on its own. You must choose among standard rules (lead and case assignment rules, escalation rules), Flow, approval processes and AI-assisted options based on what the requirement needs, and know settings such as the default automation user that keeps time-based work running. Flow is the core: screen flows for guided user interaction, record-triggered flows that run before or after a save, autolaunched flows started by other processes, and how these fit into the order of execution. Approval processes add formal sign-off with approver criteria, record locking and approval or rejection actions.
The section exists because Flow is now Salesforce's primary declarative automation tool after the retirement of Workflow Rules and Process Builder, and admins are expected to automate safely without code. It connects to Sales and Service rules, to data validation, and to Agentforce, where flows can become agent actions.
How it's tested
Questions describe a business rule and ask for the most appropriate or most efficient automation. Expect choices between flow types and trigger options, between Flow and a standard rule, and between a flow and an approval process. Read for timing, user interaction and whether the record itself or related records change.
-
Choose the tool
A requirement can be met by an assignment rule, escalation rule, flow or approval process, and the stated need for interaction, timing or sign-off decides.
-
Choose the flow type and trigger
You select screen, record-triggered or autolaunched, and for record-triggered flows whether to optimize for fast field updates or actions and related records.
-
Predict the save order
Several automations touch one record, and you work out which runs first and what the user sees, such as a validation error after a before-save update.
A requirement says that when an opportunity closes, a renewal opportunity must be created and the account's status updated. Neither change is to the triggering record, so a before-save flow cannot do it, because fast field updates only change the record being saved. An after-save record-triggered flow on Opportunity, with an entry condition for Stage changing to Closed Won, creates the renewal and updates the account.
Objectives 3
Official objectives from the Salesforce outline, in outline order.
7.1 Given a scenario, identify the appropriate automation solution based on the capabilities of the tool (escalation rules, case assignment rules, lead assignment rules, default automation user, AI).Matching each requirement to the simplest capable tool.
- What it means
- Admins choose among standard rules (lead and case assignment rules for creation-time routing, escalation rules for time-based case follow-up), Flow for general logic, approval processes for formal sign-off, and AI features where predictions or generated content help. Process Automation Settings include a default automation user (the default workflow user) that runs time-based actions when the original triggering user is inactive.
- What to understand
- Use the purpose-built rule when it fully meets the requirement, because it needs less maintenance; use Flow when logic exceeds what the rule can express. Workflow Rules and Process Builder are retired for new automation, so new answers should use Flow. AI is appropriate when the task needs prediction, classification or language, not for deterministic rules a flow can state exactly.
- How it shows up
- A scenario asks how to route leads by country on creation, and the simplest answer is a lead assignment rule rather than a record-triggered flow.
- Common confusion
- Candidates choose Flow for every scenario because it is the strategic tool; when a standard rule already matches the requirement exactly, it is usually the expected answer.
7.2 Describe capabilities, use cases, and configuration for Flow (screen flows, record-triggered flows, autolaunched flows, order of execution).Flow types, triggers, and where flows run in a save.
- What it means
- Screen flows guide users through screens and can be launched from Lightning pages, quick actions or the utility bar. Record-triggered flows start when a record is created, updated or deleted, and are optimized for fast field updates (before save, same record only) or actions and related records (after save), with optional scheduled paths. Autolaunched flows have no trigger and are started by other flows, Apex, buttons or agents, while schedule-triggered flows run on a timetable.
- What to understand
- Before-save flows run early in the order of execution, before custom validation rules, and update the triggering record without an extra save, which makes them the most efficient choice for same-record field updates. After-save flows run after the record is saved and are needed to create or update other records, send emails or call actions. Entry conditions with the option to run only when a record is updated to meet the conditions prevent repeated firing.
- How it shows up
- A requirement updates a field on the same record on every save, and the expected answer is a record-triggered flow optimized for fast field updates.
- Common confusion
- Only one version of a flow is active at a time; editing a flow creates a new version that must be activated, and the old active version keeps running until then.
7.3 Describe capabilities, use cases, and configuration for the approval process (criteria for approvers, rejections, approvals).Formal sign-off with steps, approvers and outcomes.
- What it means
- An approval process defines entry criteria, who can submit, one or more steps with their own criteria, and who approves each step: the submitter's manager, a related user, a queue or named users, with unanimous or first-response options. Initial submission actions usually lock the record, and final approval, final rejection and recall actions update fields, send emails, create tasks or send outbound messages.
- What to understand
- Records are not approved automatically by meeting criteria; they must be submitted, manually or by automation. Records stay locked while pending, so only administrators or approvers can edit them. Rejection can be final or send the request back to the previous step, depending on step settings.
- How it shows up
- Discounts above a threshold need a manager's sign-off and the record must not change while waiting, and the answer is an approval process with record locking.
- Common confusion
- A validation rule blocking high discounts is not an approval; it rejects the save outright and gives no one a way to approve an exception.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Record-triggered flow: fast field updates (before save)
A record-triggered flow that updates fields on the triggering record before it is saved.
- Remember
- It changes only the triggering record and avoids an extra save, so it is the most efficient option for same-record updates.
- Tested as
- Same-record derivation and defaulting scenarios.
- Trap
- Trying to create related records or send emails from it.
-
Record-triggered flow: actions and related records (after save)
A record-triggered flow that runs after the save and can create or update other records, send emails and call actions.
- Remember
- It can also add scheduled paths for time-based work, such as reminders days after a date.
- Tested as
- Requirements touching related records or external actions.
- Trap
- Using it for simple same-record updates and causing an unnecessary extra save.
-
Screen flow
A flow with screens that guides a user through input and decisions.
- Remember
- It needs a launch point, such as a Lightning page component, quick action or utility bar.
- Tested as
- Guided data entry or wizard-style processes.
- Trap
- Expecting it to run automatically when a record changes.
-
Autolaunched flow
A flow with no screens and no built-in trigger, started by another flow, Apex, a button or an agent action.
- Remember
- It is the reusable building block, often called as a subflow.
- Tested as
- Reusable logic shared by several processes.
- Trap
- Confusing it with a record-triggered flow, which starts on its own.
-
Schedule-triggered flow
A flow that runs at a set time and frequency, optionally over a batch of records that meet criteria.
- Remember
- Good for nightly or weekly batch updates.
- Tested as
- Recurring maintenance requirements.
- Trap
- Using it when the requirement says immediately on save.
-
Order of execution
The sequence of events on a save: before-save flows, before triggers, custom validation rules, the save, after triggers, assignment and auto-response rules, after-save flows, then roll-up updates and commit.
- Remember
- Before-save flows run before validation rules, so a value they set is checked by validation.
- Tested as
- Predicting what a user sees when several automations run on one record.
- Trap
- Assuming validation runs before any automation changes the record.
-
Entry conditions and update-only-when-met
Conditions that decide whether a record-triggered flow runs, with an option to run only when a record changes to meet them.
- Remember
- The option prevents the flow from firing on every later edit.
- Tested as
- Questions about flows sending duplicate emails or creating duplicate records.
- Trap
- Leaving the flow to run every time the record is updated while conditions stay true.
-
Default automation user
A Process Automation Settings user that runs time-based actions when the user who triggered them is inactive.
- Remember
- Set it to an active administrator-level user so scheduled work does not fail after departures.
- Tested as
- Named in the guide as an automation consideration.
- Trap
- Ignoring it until scheduled actions start failing for deactivated users.
-
Approval process
Formal sign-off with entry criteria, steps, approvers and actions on submission, approval, rejection and recall.
- Remember
- Records must be submitted, and are locked while pending by default.
- Tested as
- Discount, expense and contract sign-off scenarios.
- Trap
- Expecting criteria alone to start an approval without submission.
-
Approver options
Approvers can be the submitter's manager, a user in a related user field, a queue, or specified users, with unanimous or first-response decisions.
- Remember
- Queues and multiple approvers let groups share approval work.
- Tested as
- Questions about routing approvals to the right person.
- Trap
- Assuming the role hierarchy picks the approver automatically.
-
Flow versions and debugging
Each saved change creates a flow version; only one version is active, and Debug lets admins test with sample records.
- Remember
- Activate the new version after testing; fault paths handle errors gracefully.
- Tested as
- Troubleshooting why a change has no effect or why a flow fails.
- Trap
- Editing a flow and expecting changes to apply without activation.
-
Retired Workflow Rules and Process Builder
Legacy automation tools that Salesforce has retired for new automation in favor of Flow.
- Remember
- New automation should be built in Flow, and existing rules can be migrated with the Migrate to Flow tool.
- Tested as
- Answers that propose new workflow rules or processes are outdated.
- Trap
- Choosing Process Builder because older study material recommends it.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Before-save vs. after-save record-triggered flow vs. scheduled path
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Fast field updates (before save) | Updates the triggering record before save | Same record only; no extra save; runs before validation | Trying to create related records |
| Actions and related records (after save) | Runs after the record is saved | Updates other records, sends emails, calls actions | Using it for same-record updates |
| Scheduled path | Runs a set time after a trigger or date field | Time-based follow-up within the same flow | Building a separate scheduled flow instead |
Screen flow vs. record-triggered flow vs. autolaunched flow
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Screen flow | Interactive flow with screens | Needs a user and a launch point | Expecting it to run on record change |
| Record-triggered flow | Starts on create, update or delete | Runs without user interaction | Using it for guided data entry |
| Autolaunched flow | No trigger and no screens | Called by other flows, Apex or agents | Expecting it to start itself |
Approval process vs. validation rule vs. flow
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Approval process | Formal sign-off by designated approvers | Submission, locking and approve or reject actions | Replacing it with a blocking rule |
| Validation rule | Blocks a save that breaks a condition | No approver; no exception path | Using it when exceptions need sign-off |
| Flow | Automates updates, actions and decisions | Can submit records for approval, but has no built-in sign-off step | Rebuilding approvals by hand in Flow |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
After-save for same-record updates
- What candidates pick
- Build an after-save record-triggered flow to set a field on the record that triggered it.
- Why it looks right
- After-save flows can do everything, so they feel safe.
- Why it's wrong
- Updating the triggering record after save causes an extra save and reruns automation; a before-save flow updates it more efficiently.
Clue to watch for The only change is to a field on the same record.
-
Flow instead of a standard rule
- What candidates pick
- Create a record-triggered flow to route new cases to queues by product.
- Why it looks right
- Flow is Salesforce's strategic automation tool.
- Why it's wrong
- A case assignment rule already routes new cases by criteria with less to build and maintain.
Clue to watch for The requirement is creation-time routing to a user or queue.
-
Validation rule as approval
- What candidates pick
- Block discounts above 20% with a validation rule.
- Why it looks right
- It reliably prevents large discounts.
- Why it's wrong
- The business wants exceptions to be approved, and a validation rule has no approver or approval path.
Clue to watch for Words such as approve, sign off or manager review.
-
Criteria start the approval
- What candidates pick
- Assume records meeting the approval entry criteria are sent for approval automatically.
- Why it looks right
- Entry criteria sound like a trigger.
- Why it's wrong
- Entry criteria only decide which records can enter; submission by a user, flow or Apex starts the process.
Clue to watch for The scenario says nothing about how records are submitted.
-
Firing on every edit
- What candidates pick
- Use a record-triggered flow with entry conditions but run it every time the record is updated.
- Why it looks right
- Conditions seem enough to control it.
- Why it's wrong
- The flow fires on every later edit while conditions remain true, sending duplicate emails or creating duplicate tasks.
Clue to watch for The requirement says when the record changes to meet a condition, or only once.
-
Legacy tools
- What candidates pick
- Create a workflow rule or Process Builder process because study notes recommend them.
- Why it looks right
- Older material and existing orgs still contain them.
- Why it's wrong
- These tools are retired for new automation; Flow is the expected answer.
Clue to watch for The question asks what to build now.
Answer framework
For any automation scenario, settle the trigger, the target records and the need for human input before choosing a tool.
- Identify the trigger: a user action, a record being created or changed, a time threshold, or a schedule.
- Check whether a standard rule matches exactly, such as lead or case assignment or case escalation, and prefer it when it does.
- If a user must enter or confirm data, use a screen flow; if it runs without a user on record change, use a record-triggered flow.
- For record-triggered flows, use fast field updates when only the triggering record changes, and actions and related records for anything else, with entry conditions that fire only when needed.
- When the business requires formal sign-off, use an approval process with clear approvers and record locking, and confirm how records are submitted.
Practice question
Want more like this? The Salesforce Admin practice test has questions for every domain.
Checklist
0 of 12
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Start with Flow, because most questions here rest on it. In a practice org build one example of each type: a screen flow on a record page, a before-save flow that sets a field, an after-save flow that creates a related task, a scheduled path that sends a reminder, and an autolaunched flow called as a subflow. Use Debug on each and activate a second version to see how versions behave.
High-priority concepts are before-save versus after-save, entry conditions that fire only when a record changes to meet them, and the position of flows and validation rules in the order of execution. Sketch the save order from memory until you can place each item.
Commonly underestimated areas are approval processes and tool selection. Build an approval process with two steps, a queue approver and different rejection behavior, then submit, approve, reject and recall a record. Review assignment and escalation rules again from the Sales and Service sections, and note the default automation user setting.
Afterwards, practice scenarios by writing down trigger, target records and human input before reading the options.
FAQ
How much of the exam is Automation?
Automation is 15% of the exam, which suggests about nine of the 60 scored questions as a planning estimate.
Do I still need to know Workflow Rules and Process Builder?
The current guide's objectives name Flow, approval processes and standard rules, not workflow rules or Process Builder. Know that they are retired for new automation and that Flow is the expected answer.
When should I use a before-save flow?
Use it when the only change is to fields on the record that triggered the flow. It runs before the save, avoiding an extra save, and its updates are checked by validation rules.
Does an approval process start automatically?
No. Entry criteria decide which records can enter, but a user, a flow or Apex must submit the record for approval.
What is the default automation user?
It is the user set in Process Automation Settings to run time-based automation when the user who triggered it is no longer active, so scheduled work does not fail.
How long should I study this section?
Plan around 20 to 25 hours as an editorial estimate, with most of that time building and debugging flows.
How does Automation relate to Agentforce?
Flows can be exposed as agent actions, and the guide's tool-selection objective lists AI among the options. Knowing what a flow can do reliably helps you decide when an agent or AI feature adds value.
Other CRM & Business Applications certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
Test your Domain 7 knowledge
You have covered tool selection, screen, record-triggered and autolaunched flows, the order of execution and approval processes. Check whether you can pick the most efficient automation in timed scenarios.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the Salesforce Admin AI tutor Get any concept explained your way