10 Business Processes to Automate in Salesforce with Flow
Practical Salesforce Flow automation ideas — lead routing, handoffs, approvals, renewals and more — with what each one needs to work well.
Most teams don't need more software to get more done. They need the system they already pay for to stop relying on people to remember the next step.
Salesforce Flow can handle a surprising amount of that work. Below are ten processes that are commonly automated with Flow, what each one involves, and what has to be true for it to work.
Before you automate anything
Automation makes a process faster — including a bad one. Before building, make sure you can describe:
- The trigger — what event starts it?
- The outcome — what record changes, and who needs to know?
- The exceptions — what should not happen automatically?
If you can't answer those in a sentence each, define the process first.
1. Lead assignment and routing
The manual version: someone checks new leads and forwards them to the right rep. Automated: leads are assigned on creation by territory, product, size or round-robin, and the owner is notified. Needs: consistent lead source and region data, and a clear rule for what happens when no rule matches.
2. Lead follow-up reminders
Automated: if a lead hasn't been contacted within a set time, a scheduled path creates a task or alerts the manager. Needs: a reliable "last contacted" signal — usually activity data or a status field.
3. Opportunity stage requirements
Automated: moving to a stage requires the fields that stage depends on (decision maker, close plan, amount), using validation rules and screen flows that guide reps through what's missing. Why it matters: forecasts become trustworthy because every opportunity at a stage meets the same definition.
4. Closed-won handoff to delivery
The manual version: the rep emails onboarding with deal details. Automated: when an opportunity closes, a record-triggered flow creates the onboarding project or case, assigns an owner, copies the key details and notifies the delivery team. Needs: an object to hold onboarding work and an agreed owner for each handoff.
5. Discount and pricing approvals
Automated: quotes above a discount threshold enter an approval process, routed by amount or region. Approval or rejection updates the record and notifies the rep. The full history stays on the record. Needs: clear thresholds and named approvers (with backups for when they're away).
6. Case routing and response targets
Automated: cases from email, web forms or chat are categorised and routed to the right queue; entitlements and milestones track response and resolution targets. Needs: a small, consistent set of case categories — too many and routing breaks down.
7. Renewal and contract reminders
Automated: a scheduled flow creates a renewal opportunity and task a set number of days before contract end. Needs: reliable contract end dates on the record.
8. Customer onboarding checklists
Automated: a new customer gets a standard set of tasks or milestones, each with an owner and due date, and the account shows onboarding status at a glance. Needs: an agreed onboarding sequence — and someone who owns keeping it current.
9. Data quality guardrails
Automated: duplicate rules warn or block on entry, validation rules enforce formats, and before-save flows standardise values like country or phone format. Why it matters: every other automation on this list depends on clean data.
10. Document generation and signatures
The manual version: someone copies record data into a Word template, emails it and chases signatures. Automated: documents generate from record data at the right stage, route for approval and signature, and the signed copy files back on the record. This usually pairs Flow with a document and eSignature tool — see our guide to quote-to-contract automation.
Which automation should come first?
Rank candidates by three questions:
| Question | Favour processes that… |
|---|---|
| How often does it happen? | run daily or weekly, not quarterly |
| How costly is a miss? | lose revenue or customers when forgotten |
| How clear are the rules? | have few exceptions and agreed owners |
High frequency, high cost of failure and clear rules is the sweet spot. Lead routing, closed-won handoffs and case routing usually win.
Build it to last
- One record-triggered flow per object and timing where practical, rather than a new flow for every request.
- Before-save flows for updates to the same record; after-save for related records and notifications.
- Descriptions on every flow that say what it does and why.
- Fault paths so failures notify someone instead of failing silently.
- Test in a sandbox with realistic data — including bulk updates and integration users.
Next step
If you have a list of manual steps and aren't sure where to start, we can help you prioritise and design them. See our Salesforce automation and Flow services, or request a consultation and tell us what's still being done by hand.