Flow exports, turned into client-ready docs.
Drop a Power Automate export. Get a diagram, a review list and a document you can send. For makers and consultants.
Drop a flow export here
A package .zip, a solution .zip or a .json file. Your file is read in this page and never uploaded.
Paste a whole flow: the JSON holds triggers and actions.
Document title and purpose
This line opens the document.
Flow
Want your logo on it? Branded PDF export is part of Pro, which opens Q1 2027. See Pro
No flow loaded
Drop an export on the drop zone, choose a file or paste the JSON. The diagram, findings and document show up here.
How it works
- 1
Export the flow
In Power Automate, choose Export, then Package (.zip). For solution flows, export the solution that holds them.
- 2
Drop it here
Flowprint reads the definition, puts each container's steps in run-after order and draws the flow.
- 3
Review and send
Write the purpose line, check the findings, then copy or download the document for your client.
Free for one flow at a time
Free
- One flow at a time
- Diagram, findings, Markdown and HTML export
- Files stay in your browser
Recommended
Pro
- Document every flow in a solution in one batch
- Branded PDF export with your logo
- Custom document templates
Not for sale yet. Nothing on this page takes payment.
FAQ
Is this a security or compliance review?
No. The findings help a reviewer and they do not replace one. Nothing here is legal advice.
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 there a daily limit?
Not now. During early access the page does not count flows. You can document as many as you like, one at a time.
Sources, as of November 13, 2026
The parser and the checks follow these pages:- Schema reference guide for the Workflow Definition Language (Microsoft Learn)
- Schema reference for trigger and action types (If, Switch, Foreach, Until, Scope)
- Handle errors and exceptions (run-after statuses Succeeded, Failed, Skipped, TimedOut)
- Create, modify, or extend variables (variables inside parallel loops)
- Power Automate limits and configuration (Apply to each concurrency, default 1, range 1 to 50)
- Export and import non-solution flows (Package (.zip))
- Power CAT notes on solution layout (Workflows/*.json, properties.connectionReferences)