Download a human-readable workflow JSON from Analyze
The Analyze page can download a cleaned, human-readable JSON representation of the uploaded workflow. It is designed for review, documentation, and scoping conversations. It is not the original workflow JSON and it is not an importable package.
5 min readUpdated Jul 3, 2026AnalyzeJSON exportworkflow review
Quick answer
In shortUse the Analyze page JSON export when architects or workflow owners need a cleaned review artifact instead of the original source file.
Most likely causeThe JSON export gives reviewers a normalized view of the analyzed workflow: workflow summary, trigger, connectors, readable steps, migration status, detected targets, diagnostics, limit-risk details, and checklist items.
What to do nextCompare the affected step in Analyze, apply the fix, and then re-export or re-run analysis.
What the JSON export is for
The JSON export gives reviewers a normalized view of the analyzed workflow: workflow summary, trigger, connectors, readable steps, migration status, detected targets, diagnostics, limit-risk details, and checklist items.
Use it when a PDF is too high-level and the original source package is too noisy for a business or architecture review.
Architecture review before export.
Customer discussion of supported, partial, and unsupported steps.
Power Automate limit-risk explanation.
Documentation for UAT planning and remediation decisions.
What it is not
The human-readable JSON is not the original workflow export, not Power Automate package JSON, and not a file that should be imported into Nintex or Power Platform.
It intentionally removes implementation noise and reshapes the data for human readers. Treat it as a report artifact, not a source of truth for package generation.
How to download it
Upload a workflow and let Analyze finish.
Open the Analyze page for the workflow.
Select Download JSON near the CSV and PDF download buttons.
Share the JSON with reviewers who need step-level detail without opening the original workflow designer.
For customer delivery, pair the JSON with the PDF report. The PDF is easier for stakeholders; the JSON is better for technical review.
Related articles
Keep reading the next most relevant guides for this workflow pattern.
