Understand your Salesforce automation before you change it.
- Analyze Salesforce Flow metadata.
- Map execution paths.
- Identify potential issues.
- See which records a flow reads and writes.
- See what other automation a record change may trigger.
- AI is optional.
Analyze Salesforce Flows
Drop one .flow-meta.xml file, several flow files, or a Salesforce flows folder.
Your Flow metadata stays in your browser.
No account required. Deterministic analysis runs locally. AI is optional.
Privacy details
- Files you select, including every file in a chosen folder, are read with the browser File API.
- Files that are not .flow-meta.xml or .flow metadata are skipped.
- A single plain .xml file is still parsed, matching the one-file flow.
- Parsing and deterministic analysis happen in the browser.
- The application does not send Flow XML to a server.
- Optional AI assistance stays off until you ask. When you do, it sends structured Flow Doctor analysis to xAI. It does not send Flow XML.
- The application does not persist Flow XML.
- Clearing the analysis or reloading the page removes it from application state.
- The sample buttons load example XML included with this page. They are not files you selected.
- Export report downloads a Markdown file, and Copy report uses the browser clipboard. Neither one uploads the report.
What stays in the browser
Deterministic analysis uses the browser File API. Flow metadata is parsed in this tab, and the checks run here. Flow XML is not uploaded and is not stored on a server. Clearing the page or reloading it removes the analysis from this tab.
Optional AI
An AI request happens only after you ask. Flow Doctor then sends derived structured analysis to the configured provider. Raw Flow XML is not sent. The API key stays in memory for this page. What the provider does with that request follows that provider's policies.
Export and copy
Export report builds a Markdown file in the browser. Copy report uses the clipboard only when you choose Copy.