Introduction
Automation has become one of the most important aspects of modern Salesforce administration and development. Organizations want to reduce manual work, improve efficiency, eliminate errors, and create seamless business processes. Salesforce Flow has emerged as the primary automation tool in the Salesforce ecosystem, replacing many legacy automation solutions, including Workflow Rules and Process Builder.
The encouraging news is that you don’t need to master every advanced Flow feature to become highly effective. In fact, a small set of flow types can solve the vast majority of real-world business challenges. Whether you’re managing leads, opportunities, support cases, approvals, or integrations, understanding these Flow types can help you automate nearly everything your organization needs.
In this article, we’ll explore the 10 Salesforce Flow types that can solve approximately 95% of your automation challenges and help you build scalable, efficient Salesforce solutions.
Table of Contents
Introduction
1. Record-Triggered FlowCommon Use Cases
Why It’s Important
Example
2. Scheduled-Triggered FlowCommon Use Cases
Why It’s Important
Example
3. Screen FlowCommon Use Cases
Why It’s Important
Example
4. Auto-Launched FlowCommon Use Cases
Why It’s Important
Example
5. Approval Process Flow IntegrationCommon Use Cases
Why It’s Important
Example
6. Platform Event-Triggered FlowCommon Use Cases
Why It’s Important
Example
7. SubflowCommon Use Cases
Why It’s Important
Example
8. Before-Save FlowCommon Use Cases
Why It’s Important
Example
9. After-Save FlowCommon Use Cases
Why It’s Important
Example
10. Flow OrchestrationCommon Use Cases
Why It’s Important
Example
Best Practices for Using Salesforce FlowsKeep Flows Simple
Use Subflows
Optimize Performance
Document Your Automation
Test Thoroughly
Monitor and Maintain
Common Problems These Flow Types Can Solve
Conclusion
1. Record-Triggered Flow
Record-Triggered Flow is the most commonly used Flow type in Salesforce. It runs automatically whenever a record is created, updated, or deleted.
Common Use Cases
Auto-assign leads to sales representatives
Update related records
Send notifications when records change
Create follow-up tasks automatically
Update opportunity stages
Why It’s Important
Most business processes revolve around record changes. Instead of relying on manual actions, record-triggered flows ensure that automation happens instantly and consistently.
Example
When a new lead is created with a specific industry value, Salesforce can automatically assign it to the appropriate sales team and create a follow-up task.
2. Scheduled-Triggered Flow
Scheduled Flows run automatically at a specific date and time or on recurring schedules.
Common Use Cases
Send renewal reminders
Update inactive customer records
Generate periodic reports
Escalate overdue cases
Archive old records
Why It’s Important
Not all automation needs to happen immediately. Some business processes require daily, weekly, or monthly execution.
Example
A scheduled flow can identify opportunities with no activity in the past 30 days and notify the opportunity owner to take action.
3. Screen Flow
Screen Flows provide a guided user interface that collects information and performs actions based on user input.
Common Use Cases
Employee onboarding
Customer support processes
Data collection forms
Guided sales processes
Internal request systems
Why It’s Important
Screen flows make complex processes easier for users by presenting step-by-step instructions and reducing errors.
Example
A service agent can use a screen flow to quickly create a case, verify customer information, and launch troubleshooting actions from a single interface.
4. Auto-Launched Flow
An auto-launched flow runs in the background without displaying screens to users.
Common Use Cases
Complex business logic
Reusable automation components
Integration processes
Data transformation
Backend processing
Why It’s Important
These flows allow administrators and developers to create modular automation that can be reused across multiple processes.
Example
An organization may use an auto-launched flow to calculate customer scores based on various criteria and update records automatically.
5. Approval Process Flow Integration
Although approval processes still exist, flows can significantly enhance approval-related automation.
Common Use Cases
Submit records for approval
Send approval notifications
Update records after approval
Create approval-related tasks
Escalate pending approvals
Why It’s Important
Combining Flow with approvals creates more dynamic and flexible business processes.
Example
When a discount exceeds a certain threshold, a flow automatically submits the opportunity for management approval and notifies the approver.
6. Platform Event-Triggered Flow
Platform Event Flows respond to platform events and enable event-driven automation.
Common Use Cases
Real-time integrations
External system communication
Order processing
Financial transactions
IoT-based actions
Why It’s Important
Modern businesses rely heavily on multiple connected systems. Platform Events help Salesforce react instantly to changes happening outside the platform.
Example
An e-commerce system sends an event when an order is completed, and Salesforce automatically updates customer records and creates follow-up activities.
7. Subflow
Subflows allow you to reuse Flow logic across multiple automations.
Common Use Cases
Shared business logic
Standardized calculations
Reusable notification processes
Common record updates
Data validation
Why It’s Important
Subflows reduce duplication and make automation easier to maintain.
Example
Instead of creating separate email notification logic in multiple flows, a company can build one subflow and reuse it everywhere.
8. Before-Save Flow
Before-Save Record-Triggered Flows run before a record is committed to the database.
Common Use Cases
Field updates
Data formatting
Validation logic
Default value assignments
Data standardization
Why It’s Important
Before-Save Flows are significantly faster than many other automation methods because they update records before the save operation completes.
Example
When a contact record is created, a Before-Save Flow automatically formats phone numbers and standardises naming conventions.
9. After-Save Flow
After-Save Flows run after the record has been saved and are ideal for actions involving related records.
Common Use Cases
Creating related records
Sending notifications
Posting to collaboration tools
Updating parent records
Triggering external actions
Why It’s Important
Many business processes depend on actions that occur after a record exists in the database.
Example
When you mark an opportunity as Closed Won, an After-Save Flow can automatically create a project record, notify stakeholders, and initiate onboarding tasks.
10. Flow Orchestration
Flow Orchestration helps manage multi-step processes involving multiple users and departments.
Common Use Cases
Employee onboarding
Customer onboarding
Contract approvals
Procurement processes
Multi-department workflows
Why It’s Important
Business processes often require coordination between several teams. Flow Orchestration ensures that every participant completes their tasks in the correct sequence.
Example
A new employee onboarding process may require actions from HR, IT, finance, and management. Flow Orchestration coordinates all tasks automatically and tracks progress.
Best Practices for Using Salesforce Flows
To maximise the effectiveness of your Flow implementations, please follow these best practices:
Keep Flows Simple
Break large automations into smaller, manageable components whenever possible.
Use Subflows
Avoid duplicating logic across multiple flows by creating reusable components.
Optimize Performance
Use Before-Save Flows for field updates whenever possible because they are faster and more efficient.
Document Your Automation
Maintain clear documentation so future administrators and developers can understand the logic.
Test Thoroughly
Always validate flows in a sandbox environment before deploying to production.
Monitor and Maintain
Regularly review automation performance and update flows as business requirements evolve.
Common Problems These Flow Types Can Solve
By mastering these 10 flow types, organizations can automate:
Lead assignment and routing
Opportunity management
Case escalation
Customer onboarding
Employee onboarding
Approval workflows
Data cleanup
Renewal management
Customer communications
Integration processes
Compliance tracking
Task automation
Together, these automations cover the vast majority of operational requirements encountered by Salesforce teams.
Conclusion
Salesforce Flow has become the foundation of automation within the Salesforce platform. While Salesforce offers numerous automation capabilities, the reality is that mastering these 10 Flow types will solve approximately 95% of the business challenges most organizations face.
Record-Triggered Flows handle everyday automation, Scheduled Flows manage recurring tasks, Screen Flows improve user experiences, and Flow Orchestration coordinates complex business processes. Combined with Subflows, Platform Events, and Auto-Launched Flows, they create a powerful automation toolkit capable of transforming how businesses operate.
Whether you’re a Salesforce administrator, consultant, or developer, investing time in these Flow types will dramatically increase your ability to deliver scalable, efficient, and future-ready Salesforce solutions. By leveraging them effectively, you can reduce manual effort, improve data quality, accelerate business processes, and unlock the full potential of the Salesforce platform.
Part of the team turning Salesforce and AI strategy into shipped, measurable outcomes for enterprises across five regions.
