What should a Salesforce Flow inventory tool surface?

A useful Flow inventory tool should surface Flow name, type (Record-Triggered, Screen, Auto-launched, Scheduled, etc.), object context, and active/inactive status for each Flow in scope. For record-triggered Flows, trigger conditions and entry conditions where visible in metadata are useful context signals for change-risk assessment.

Why is a Flow inventory important before making changes?

Flows are the primary Salesforce automation layer for most orgs built after Salesforce deprecated workflow rules and process builders. In an org with years of accumulated changes, the same object may have multiple active record-triggered Flows running in an order that is not always predictable from Setup. Knowing what is there before you add, modify, or deactivate a Flow reduces the risk of interaction failures.

Does KeelCadence's Automation Inventory cover all Flow metadata?

The Automation Inventory workbook surfaces available Flow metadata — type, status, object, and entry condition fields where exposed. It does not fully document nested subflows, dynamic action calls, or Apex invocations inside a Flow. Those require direct Flow Builder review for thorough analysis.

Should I review inactive Flows before cleanup?

Yes. An inactive Flow is not a safe-to-delete Flow. Inactive Flows may have been deactivated temporarily during a deployment, may be staging versions of active Flows, or may have been turned off during a debugging session and never reactivated. The inventory should include inactive Flows as a distinct review category.

How does a Flow inventory relate to field cleanup?

Flows can reference specific fields. If you are planning to remove or modify a field, checking whether any active or inactive Flow references that field before proceeding is a key step in the cleanup review. The Automation Inventory workbook gives you the Flow list for selected objects so you know what to check manually in Flow Builder.

Do I need to install a Salesforce package to run a Flow inventory with KeelCadence?

No. KeelCadence does not require a package install, Connected App, or persistent OAuth token. The Automation Inventory runs read-only for the session and does not export customer record data.

Tool Guide · Flow Inventory

WHAT A SALESFORCE FLOW INVENTORY SHOULD SURFACE BEFORE YOU CHANGE AUTOMATION.

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

01 — The Flow Accumulation Problem

FLOWS ACCUMULATE. DOCUMENTATION DOES NOT.

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.

02 — What This Helps You Review

FLOW INVENTORY SIGNALS FROM THE AUTOMATION WORKBOOK.

What this helps you review

Flow inventory by object — all Flows associated with selected objects
Flow type — Record-Triggered, Screen, Auto-launched, Scheduled, and other types
Active vs. inactive status as a first-pass cleanup candidate signal
Entry conditions and trigger type metadata where visible
Flow count by object as a complexity and change-risk reference signal
Legacy automation (workflow rules, process builders) on the same objects

Relevant Workbook

Automation Inventory

The Automation Inventory workbook surfaces Flow metadata alongside Apex, validation rules, approval processes, and legacy automation for selected objects — formatted for pre-change review.

Learn more →Run diagnostic →View sample workbook →

03 — Inactive Flows

DO NOT TREAT INACTIVE FLOWS AS ALREADY CLEANED UP.

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.

Before removing an inactive Flow

Check whether it was recently deactivated — not all deactivations are permanent
Check whether it is a version of an active Flow still in use
Check whether it is referenced by a subflow invocation in another active Flow
Document the review decision with the rationale for removal

04 — Related Resources

RELATED GUIDES.

Salesforce Automation Inventory Guide — the full automation inventory guide covering all automation layers.
Salesforce Automation Inventory Tool — what a complete automation inventory tool should surface.
Automation Review Before Making Changes — what to check before modifying Flows, Apex, or validation rules.
Import & UAT Readiness Checklist — record readiness factors including validation rules and required fields that interact with Flows.
All Resources

FAQ

FREQUENTLY ASKED QUESTIONS.

What should a Salesforce Flow inventory tool surface?: A useful Flow inventory tool should surface Flow name, type (Record-Triggered, Screen, Auto-launched, Scheduled, etc.), object context, and active/inactive status for each Flow in scope. For record-triggered Flows, trigger conditions and entry conditions where visible in metadata are useful context signals for change-risk assessment.
Why is a Flow inventory important before making changes?: Flows are the primary Salesforce automation layer for most orgs built after Salesforce deprecated workflow rules and process builders. In an org with years of accumulated changes, the same object may have multiple active record-triggered Flows running in an order that is not always predictable from Setup. Knowing what is there before you add, modify, or deactivate a Flow reduces the risk of interaction failures.
Does KeelCadence's Automation Inventory cover all Flow metadata?: The Automation Inventory workbook surfaces available Flow metadata — type, status, object, and entry condition fields where exposed. It does not fully document nested subflows, dynamic action calls, or Apex invocations inside a Flow. Those require direct Flow Builder review for thorough analysis.
Should I review inactive Flows before cleanup?: Yes. An inactive Flow is not a safe-to-delete Flow. Inactive Flows may have been deactivated temporarily during a deployment, may be staging versions of active Flows, or may have been turned off during a debugging session and never reactivated. The inventory should include inactive Flows as a distinct review category.
How does a Flow inventory relate to field cleanup?: Flows can reference specific fields. If you are planning to remove or modify a field, checking whether any active or inactive Flow references that field before proceeding is a key step in the cleanup review. The Automation Inventory workbook gives you the Flow list for selected objects so you know what to check manually in Flow Builder.
Do I need to install a Salesforce package to run a Flow inventory with KeelCadence?: No. KeelCadence does not require a package install, Connected App, or persistent OAuth token. The Automation Inventory runs read-only for the session and does not export customer record data.

Before You Change Automation

INVENTORY YOUR AUTOMATION BEFORE THE NEXT 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.

Run Automation Inventory View sample workbook

See what Automation Inventory covers →

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.