Definition
Flows is the main Setup page that lists all Flows in the org, including their type (Screen Flow, Record-Triggered Flow, Autolaunched Flow, etc.), status (Active, Inactive, Draft), and version history. From this page, administrators can create new Flows, activate or deactivate existing ones, and access Flow Builder.
Real-World Example
The admin at Forge Dynamics opens the Flows page in Setup and filters by "Active" status to review all 45 active Flows in the org. She notices an old Screen Flow that was replaced by a newer version and deactivates it. She then clicks "New Flow" to begin building a Record-Triggered Flow for automatically updating Account ratings.
Why Flows Matters
The Flows page in Salesforce Setup is the central management console for all automation built with Flow Builder. It lists every flow in the org — Screen Flows for guided user experiences, Record-Triggered Flows for automated backend processing, Autolaunched Flows for headless logic, and Scheduled Flows for time-based operations. Admins can filter by status (Active, Inactive, Draft), view version history, and quickly identify which flows are running in production. This single pane of glass solves the problem of automation sprawl by giving admins visibility into every automated process.
As orgs mature, the Flows page often contains dozens or even hundreds of flows. Without regular housekeeping, inactive and draft flows accumulate, making it difficult to find and manage active automations. Admins should establish a naming convention (e.g., Object_Trigger_Purpose), periodically deactivate deprecated flows, and use version history to roll back problematic changes. Organizations that neglect flow management risk deploying conflicting automations, confusing new admins who inherit the org, and making troubleshooting exponentially harder during critical incidents.
How Organizations Use Flows
- Vanguard Realty — The Salesforce admin opens the Flows page weekly to audit the 62 active flows across the org. She filters by 'Record-Triggered Flow' type and discovers three flows on the Opportunity object that were built by different team members with overlapping logic. She consolidates them into a single flow, reducing execution time by 40%.
- Cascade Education — During a system performance review, the IT director uses the Flows page to identify 28 inactive flows that were never cleaned up after a major platform migration. Removing these unused flows simplifies the org, reduces confusion during troubleshooting, and makes the deployment pipeline faster because fewer metadata components need to be tracked.
- Apex Dynamics Manufacturing — A newly hired admin at Apex Dynamics uses the Flows page to onboard herself by reviewing the version history of each active flow. She traces how the lead routing flow evolved over six versions, understanding why certain business rules were added. This self-service documentation saves her two weeks of ramp-up time compared to the previous admin hire.