Analyze & compatibility
Understand supported, partial, best-effort, and premium connector 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 that view with confidence.
Articles in Analyze & compatibility
Read the full set, or start with the featured guides if you are new to this topic.
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 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.
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.
Search the knowledge base
Search across all categories if this topic is close, but not quite the right fit.
All categories
Start here
These guides usually answer the first two or three questions users ask in this category.
Recently updated in this category
Need a real workflow reviewed?
Public articles are great for recurring patterns. If you have a workflow export and want advice on the exact blockers, contact us with the workflow and the Analyze report.

