WHAT A SALESFORCE AUTOMATION INVENTORY TOOL SHOULD SURFACE BEFORE YOU TOUCH ANYTHING.

AUTOMATION IN SALESFORCE IS SPREAD ACROSS TOO MANY LAYERS TO REVIEW MANUALLY.

In an org that has been in active use for a few years, automation typically lives in multiple places: Screen Flows, Record-Triggered Flows, Auto-launched Flows, Apex triggers, Apex batch jobs, workflow rules, process builders, validation rules, and approval processes. These are built by different people at different times, and they rarely reference each other in any documentation that survives.

Before changing anything — adding a field, modifying a record type, updating a validation rule — it is worth knowing what is already running on the objects you are about to touch. An automation inventory gives you that baseline.

The inventory does not tell you what to change. It tells you what exists before you decide.

WHAT THE AUTOMATION INVENTORY WORKBOOK SURFACES.

WHAT AN AUTOMATION INVENTORY DOES NOT FULLY MAP.

The inventory is a structured starting point for the review — not a substitute for it. Use the workbook to know what you are dealing with, then proceed with the appropriate level of review given the scope of your change.

PAIR INVENTORY WITH IMPACT AWARENESS FOR CHANGE WORK.

Knowing what automation exists is the first step. Knowing which objects are safe to import records into, run UAT against, or push changes to requires a second layer of review: required fields, restricted picklists, record type configurations, and validation rule logic that affects record-save behavior.

RELATED GUIDES.

• Salesforce Automation Inventory Guide — how to review available automation metadata before making changes.
• Automation Review Before Making Changes — what to look at before touching Flows, Apex, or validation rules.
• Salesforce Flow Inventory Tool — focused guide for Flow-specific inventory and review.
• Import & UAT Readiness Checklist — what to review before loading records or creating test data.
• All Resources

FREQUENTLY ASKED QUESTIONS.

What should a Salesforce automation inventory tool surface?

A useful automation inventory tool should surface available metadata across Flows, Apex classes and triggers, validation rules, workflow rules, process builders, and approval processes for selected objects. It should flag active versus inactive automation, entry conditions where visible in metadata, and automation count by object — so admins have a working inventory before making changes.

Why is it hard to get a complete Salesforce automation inventory?

Salesforce automation runs across multiple layers: declarative tools like Flows and validation rules, programmatic tools like Apex, legacy tools like workflow rules and process builders, and platform tools like approval processes. These are maintained in different areas of Setup and are rarely documented together. An inventory effort that only looks at Flows misses a significant portion of the automation that can affect record behavior.

Does KeelCadence's Automation Inventory fully map automation dependencies?

No. The workbook surfaces available automation metadata for selected objects — what is present, what is active, and key metadata fields where they are exposed. It is a first-pass inventory, not a complete runtime dependency map. Dependencies that are only visible at runtime or are embedded in Apex logic require code review beyond what metadata surfaces.

When should I run an automation inventory?

Before changing any automation in an inherited or unfamiliar org. Before adding new automation to objects with existing process logic. Before imports or UAT where automation may trigger on new records. Before cleanup work on fields or objects that may be referenced in automation. Running the inventory first gives you a structured baseline.

Do I need a Salesforce package to run an automation 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.