Key takeaways
- Start with automations that remove repetitive data entry: routing, follow-up tasks and renewals.
- Use one record-triggered Flow per object and trigger type where possible, with clear entry conditions.
- Workflow Rules and Process Builder are no longer supported. Migrate them to Flow before something breaks.
- Test in a sandbox and document every Flow in its description field.
Small sales teams lose a surprising amount of time to copying data between records, creating the same tasks and chasing approvals. Salesforce Flow can take most of that off their plate without any code.
Below are ten automations we recommend most often, followed by a few rules that keep them from becoming a problem.
1. Lead assignment by territory or round-robin
New leads land with the right person within seconds. A record-triggered Flow on Lead can assign by country, industry or company size, or rotate between reps using a simple counter.
2. Follow-up tasks when a stage changes
When an opportunity moves to Proposal, create a task to follow up in three days. When it moves to Negotiation, create a task for a contract review. Reps stop relying on memory.
3. Required next step on key stages
Instead of a validation rule that blocks saving, use a screen Flow or a dynamic form section that asks for the next step and its date when a deal reaches a later stage. Managers get the information without frustrating reps.
4. Discount approvals
If a discount exceeds a threshold, submit the opportunity for approval automatically and notify the manager in Salesforce or Slack. Approved discounts are recorded on the record, which helps later when you analyse margins.
5. Renewal opportunities
When a deal closes won with a contract end date, create a renewal opportunity scheduled 90 days before that date. Recurring revenue stops depending on someone's calendar reminder.
6. Handover to delivery or onboarding
On closed won, create the onboarding record or project, assign the owner and post a summary to the delivery team. This is one of the most valued automations in service businesses.
7. Stale deal alerts
A scheduled Flow runs every Monday, finds open opportunities with no activity for 14 days or a close date in the past, and sends each owner a list. Pipeline stays honest without manual reviews.
8. Contact role reminders
Deals with one contact are riskier than deals with several. A Flow can check contact roles at a given stage and remind the rep to add the decision maker.
9. Data clean-up on save
Standardise country names, capitalise company names, copy the industry from account to opportunity. Small corrections on save improve reports without anyone noticing the work.
10. Customer case routing
If your team also uses Service Cloud, route new cases by product or priority and escalate cases that have not been touched within the agreed time.
Rules for safe automation
One Flow per object and trigger, where practical. Several Flows, triggers and old automations on the same object make it hard to predict what runs first. Use entry conditions to keep each Flow focused, and set a trigger order when you must have more than one.
Before-save for field updates. Updating fields on the same record is faster in a before-save Flow, because it avoids an extra save.
Handle errors. Add fault paths to elements that can fail, and route error emails to someone who will read them.
Describe every Flow. Fill in the description field with what the Flow does, who requested it and when. Future admins will thank you.
Test in a sandbox. Test with realistic data and with a user who has a rep's permissions, not only as an admin.
Migrating from Workflow Rules and Process Builder
Salesforce ended support for Workflow Rules and Process Builder on 31 December 2025. Existing automations keep running, but bugs that appear will not be fixed (details from SalesforceTime). The safest approach:
- List every active Workflow Rule and Process Builder with what it does.
- Remove what is no longer needed. Many orgs find a third of them can go.
- Use Salesforce's Migrate to Flow tool for simple ones, and rebuild complex ones by hand.
- Consolidate per object rather than converting one to one.
- Test, deploy and deactivate the old automation in the same release.
If you'd like help choosing which of these ten automations fit your process, or with a Process Builder migration, the automation service covers design, build, testing and documentation.
Frequently asked questions
Do I need a developer to build Salesforce Flows?
No. Flow is a declarative tool built for admins. You need a developer only for logic Flow can't handle well, such as complex calculations on large data volumes or certain integrations.
What happens to our old Workflow Rules and Process Builders?
They keep running, but Salesforce ended support for them on 31 December 2025, so bugs will not be fixed. Salesforce provides a Migrate to Flow tool that converts many of them automatically; complex ones need manual rebuilding.