Flows are the primary automation layer in most active Salesforce orgs. Before adding, modifying, or deactivating a Flow — especially on a heavily customized object — knowing what is already running on that object gives you the context you need to avoid unexpected interactions.
Read-only diagnostics · Review-ready workbooks · No package install · No Connected App
In an org that has been in use for several years, Flows accumulate in layers. An admin builds a record-triggered Flow for a sales process. A consultant adds a screen Flow for a guided intake form. A developer adds an auto-launched Flow invoked from Apex. A migration adds a scheduled Flow that runs nightly on a batch of records.
Each of these was built in isolation. None of them is documented in a central location. And when a new admin or consultant inherits the org, none of them is obvious from the object list or the Setup menu unless you know where to look.
A Flow inventory gives you the list before you touch anything. It does not tell you what each Flow does in full detail — but it tells you what exists so you can make an informed decision about how carefully to review before proceeding.
Relevant Workbook
The Automation Inventory workbook surfaces Flow metadata alongside Apex, validation rules, approval processes, and legacy automation for selected objects — formatted for pre-change review.
An inactive Flow is not a decommissioned Flow. In many orgs, inactive Flows are deactivated-for-now: paused during a deployment, in a debugging cycle, or waiting to be reactivated after a dependent change. An inactive Flow that you delete during a cleanup project may be the Flow that was about to be turned back on.
The inventory should flag inactive Flows as a distinct review category. For each inactive Flow, the relevant question is whether it is intentionally inactive, temporarily inactive, or genuinely obsolete. That determination requires stakeholder input — the metadata alone does not answer it.
Editing an inherited Flow without context is how a small change becomes a record-save failure or a silent data problem. Before you open a Flow you did not build, gather the surrounding metadata so you understand what it touches and what depends on it.
The inventory tells you a Flow exists. Reviewing these signals tells you whether it is safe to change.
A Flow-only review is enough when your change is contained to one Flow on one object. Two patterns tell you the review needs to widen before you touch anything:
When either pattern applies, move from a Flow list to a full automation inventory that shows Flows alongside Apex, validation rules, and approval processes grouped by object. That is the view the Automation Inventory workbook is built to give you before a change.
KeelCadence Automation Inventory surfaces Flow metadata alongside Apex, validation rules, and approval processes — formatted as a structured XLSX workbook for pre-change review across selected objects.
Opens automation.keelcadence.com. Best run from desktop, since the diagnostic uses your active Salesforce browser session. On mobile, view the sample workbook or save this page for later.
Read-only · No package install · No Connected App setup · No Salesforce writes
KeelCadence uses session cookies and Google Analytics 4 for site usage insights. GA4 does not receive Salesforce credentials, Org IDs, Report IDs, or payment data. You can opt out for this browser.