Detect unsafe contexts, queries in loops, hardcoded IDs, and more to optimize Salesforce Flows.
Lightning Flow Scanner App integrates the Lightning Flow Scanner as a UMD module within Salesforce, enabling scanning of flow metadata for 20+ issues such as hardcoded IDs, unsafe contexts, inefficient SOQL/DML operations, recursion risks, and missing fault handling.
For details about all available rules, their default severities, and configuration options, visit the Flow Scanner Documentation.
Prerequisite: Ensure that the Flow Scanner permission set is assigned to users who need access.
- Click on the App Launcher icon in the top-left corner of your Salesforce interface.
- Search for "Flow Scanner" in the App Launcher.
- Click on the "Flow Scanner" app to open the Scan Flows Overview.
- (Optional) Configure rules in the Configuration tab.
- View results of a Flow by clicking "details".
Privacy: Zero user data collected. All processing is client-side. → See Data Handling in our Security Policy.
While no configuration is required, Admins can define default severities, expressions, or disabled states for scan rules using the ScanRuleConfiguration__mdt custom metadata type. These overrides apply globally for all users in the org, but individual users can still adjust severities or disable rules locally in the browser — those changes only persist for their current session. For a more on configurations, review the documentation.
- Go to Setup → Custom Metadata Types → ScanRuleConfiguration → Manage Records
- Click New and set the following fields:
- Rule Name — must match the rule’s API name (e.g.,
FlowName) - Severity —
Error,Warning,Info, orNote - Expression (optional) — e.g.,
[A-Za-z]+_[0-9]+ - Disabled — check to turn off the rule globally
- Once saved, the Flow Scanner App automatically applies these overrides at load time — no user configuration needed.
Or via Salesforce CLI:
sf package install --package [email protected] --wait 10- Clone this repository:
git clone https://github.com/Flow-Scanner/lightning-flow-scanner-app.git- Create a Scratch Org
sf org:create:scratch --definition-file config/project-scratch-def.json --alias FlowScanner --duration-days 7 --set-default --json- Push Source to Your Org:
sf project:deploy:start- Assign Permission Set
sf org assign permset --name Flow_ScannerWant to help improve Lightning Flow Scanner? See our Contributing Guidelines