Document your flows

The Flow Documentation tool, new in v1.2.0, turns Power Automate flow definitions into self-contained, interactive HTML pages. It works from exported flow .json files, from solution .zip packages, or directly from a connected environment. Output is HTML only in 1.2.0; Markdown and Word export are not available in this release.

Document local files

Export flows from the Power Automate portal, or export a solution from the Power Apps maker portal, then:

  1. Open Flow Documentation from the sidebar, under the Automation category.
  2. Stay on the Local Files tab.
  3. Click Add Flow JSON and pick one or more exported flow .json files, or click Add Solution ZIP and pick a solution package. You can mix both in the list and remove entries with the X.
  4. Click Generate HTML.

Each .json file produces one HTML page in the output folder. A solution .zip produces a subfolder named after the package, with an index.html solution overview and one page per flow the package contains.

Document a connected environment

This mode needs a working sign-in; see Choose a sign-in method.

  1. Open Flow Documentation and switch to the Connected Environment tab.
  2. Paste the environment GUID into the Environment GUID field.
  3. Click Load Flows and wait for the list to fill.
  4. Select a flow and click Generate HTML.

The tool downloads the flow definition and writes the same kind of page as for local files. Connected mode documents one selected flow at a time.

Choose the output folder

The default output folder is %TEMP%\PowerToolBox\FlowDocs. Click Browse… to pick a different folder before generating. The status line at the bottom of the tool shows where the files were written.

What the pages contain

Each page is a single .html file you can open in any browser and share like any other file: an interactive diagram of the flow’s triggers and actions, the details of each step, and the flow definition.

Two safeguards apply automatically:

  • Secret redaction. Passwords, tokens, API keys, connection strings, and similar values are replaced with ******* before anything is written. Redaction runs during extraction, so it covers local files and connected downloads alike.
  • Connector icons. When icons are present in the local cache at %APPDATA%\PowerToolBox\ConnectorIcons, pages embed them as images. Icon downloads are restricted to allow-listed Microsoft hosts over HTTPS.

Not in 1.2.0

  • Markdown and Word export (deferred).
  • AI-written summaries of flows and steps (deferred).

See Known limitations in 1.2.0 for the full list.

Last updated: July 27, 2026