Turn an exported cloud flow into documentation you can hand to a client.

Drop a Power Automate export or paste the definition JSON. Flowprint draws the flow, writes the document in Markdown and HTML, and lists what a reviewer would flag. It runs in this page, so your flow is never uploaded.

Reads
Package .zip (legacy export), solution .zip, definition.json, or a raw workflow definition.
Writes
A diagram, a Markdown document and a standalone HTML document.
Checks
Failure paths, hard-coded emails and URLs, default step names, deep nesting, loop concurrency.

Drop a flow export

A .zip package, a solution .zip, or a .json file.

The free plan documents one flow at a time. Batch documentation of a whole solution is part of Pro, which opens Q1 2027.

Example flow Sample data written for this demo. It is not from a real tenant. Load your own export above to replace it.

Flow

Trigger
-
Actions
0
Connectors
0
Max nesting depth
0

Diagram

How it works

1

Export the flow

In Power Automate, choose Export and then Package (.zip). For solution flows, export the solution that holds them.

2

Drop it here

Flowprint reads the definition, orders each container's steps by their run-after settings and draws the flow.

3

Review and send

Write the purpose line, check the findings, then copy or download the document for your client.

Pricing

Free

$0
  • One flow at a time
  • Up to 3 flows per day
  • Diagram, findings, Markdown and HTML export
Use the tool

Pro

$8.99 per month
  • Document every flow in a solution in one batch
  • Branded PDF export with your logo
  • Custom document templates
Opens Q1 2027

FAQ

Does my flow leave the browser?
No. The file is read by JavaScript on your device. The page loads its fonts from Google Fonts and the JSZip library from cdnjs. It sends nothing else anywhere.
Which files work?
A package from Export, Package (.zip). A solution .zip with flows in its Workflows folder. The definition.json from inside a package. A workflow definition pasted as JSON. Desktop flows and classic Dataverse workflows are not supported.
How exact is the diagram?
Each container's steps are drawn top to bottom in run-after order. When a step runs in parallel, or only after a failure, its arrow carries a label. Parallel branches are not drawn as separate lanes.
How are findings decided?
They are pattern checks on the definition. Default names are matched against a list of common designer names. Emails and URLs are found by pattern in step inputs. Each check is listed with the steps it found.
Is the free limit enforced?
Not yet. During early access the page does not count flows, so you can document more than 3 a day.
Is this a security or compliance review?
No. The findings help a reviewer and they do not replace one. Nothing here is legal advice.
Sources, as of November 13, 2026. The parser and the checks follow these pages: