Understand supported, partial, best-effort, premium connector, and Power Automate platform-limit behavior before you export.
The Analyze step is where users decide whether a workflow is a quick win, a partial conversion, or a manual rebuild. This section explains how to read coverage, platform-limit risk, connector exposure, and action-decoder guidance with confidence.
Articles in this category
Browse all guides in Analyze & compatibility.
Download a human-readable workflow JSON from Analyze
Use the Analyze page JSON export when architects or workflow owners need a cleaned review artifact instead of the original source file.
Why HTTP may show as supported but premium
HTTP steps can be supported even when they are premium; the important question is whether method, URI, auth, and payload can be represented cleanly.
How Nintex for SharePoint bulk updates, collections, and web services are converted
Understand the new .nwf coverage for Update multiple items, Collection operation, Call web service, and Action set patterns.
Recent supported action coverage updates
Review the major action families recently moved into supported coverage across SharePoint, Nintex for SharePoint, Salesforce, Office 365 Users, Nintex Tables, custom APIs, data operations, and workflow control.
How to use compatibility search and action decoder pages
Search Nintex action mappings and open action-specific decoder pages that explain support level, target action, and remediation notes.
What does “Partial” mean in Analyze?
Understand when Partial means light review, when it means a strategy choice, and when it still points to real manual work.
Why the trigger appears first in Analyze
The trigger is shown as the first workflow row because users expect execution order, not a separate metadata card.