Compatibility
Compatibility matrix
Last updated: April 3, 2026Current support for converting Nintex Automation Cloud exports and Nintex for SharePoint workflows (.nwf/.wf) into Power Automate. “Supported” means we can emit the logic into the generated flow (and generate an importable package when supported). Some supported items are best-effort and still deserve post-import review, especially tasks, HTTP, document generation, and database-backed actions. “Partial” means conversion runs but needs manual adjustment or a target-side replacement. “Planned” means Flow Migrator has not mapped the item yet. “Not available” means the target Power Automate connector does not offer an equivalent action today. Need the full migration overview first? See how to convert Nintex workflows to Power Automate.
Triggers
6 Supported5 Partial0 Planned0 Not available
Grouped by connector for a cleaner scan.
Actions
105 Supported4 Partial7 Planned7 Not available
Expand only the connectors you care about.
Legend
SupportedPartialPlannedNot available
Status is shown per item with notes where relevant.
Export support
Power Automate ZIP generation is supported for both Nintex Automation Cloud exports (ZIP containing workflows/<GUID>/design.json) and Nintex for SharePoint workflows (.nwf/.wf) in cloud or on‑prem environments.
Focused guidance for list, library, item, file, and SharePoint-heavy migration patterns.
Planning guidance for routing, reminders, waits, branches, and decision-heavy migrations.
Connector-specific guidance for notification-heavy and Exchange-oriented workflow logic.
Use-case guidance for collaboration workflows that touch Teams, channels, and cross-surface actions.
Triggers
Expand a connector group to view the current status for each trigger.
| Trigger | Status | Notes |
|---|
| File created | Partial | Converted using polling template (Recurrence + List files). Power Automate has no native Google Drive triggers. |
| File moved to trash | Partial | Converted using polling template (Recurrence + List files). Power Automate has no native Google Drive triggers. |
| Folder created | Partial | Converted using polling template (Recurrence + List files). Power Automate has no native Google Drive triggers. |
| Folder moved to trash | Partial | Converted using polling template (Recurrence + List files). Power Automate has no native Google Drive triggers. |
Microsoft Exchange Online
1 items
| Trigger | Status | Notes |
|---|
| Received email | Supported | — |
OneDrive for Business
2 items
| Trigger | Status | Notes |
|---|
| New file | Supported | — |
| New folder | Partial | May require manual selection after import. |
| Trigger | Status | Notes |
|---|
| Scheduled start | Supported | — |
| Trigger | Status | Notes |
|---|
| New list item | Supported | — |
| New or updated list item | Supported | — |
| Updated list item | Supported | — |
Actions
Expand a connector group to view the current status for each action.
| Action | Status | Notes |
|---|
| Create an approval | Supported | — |
| Start and wait for an approval | Supported | — |
| Action | Status | Notes |
|---|
| Complex joined / aggregate / vendor-specific queries | Partial | Complex FRN and IBM i query patterns may still require manual conversion. |
| Delete row | Supported | Simple table and CRUD patterns only. |
| Get row | Supported | Simple table and CRUD patterns only. |
| Get rows | Supported | Simple table and CRUD patterns only. |
| Get tables | Supported | Simple table and CRUD patterns only. |
| Insert row | Supported | Simple table and CRUD patterns only. |
| Update row | Supported | Simple table and CRUD patterns only. |
| Action | Status | Notes |
|---|
| Copy a file | Supported | — |
| Create a file | Supported | — |
| Create a folder | Not available | Power Automate's Google Drive connector does not offer an equivalent action. |
| Delete a file | Supported | — |
| Get drives | Not available | Power Automate's Google Drive connector does not offer an equivalent action. |
| Get file content | Supported | — |
| Get file content by path | Supported | — |
| Get file metadata | Supported | — |
| Get file metadata by path | Supported | — |
| List files in folder | Supported | — |
| List files in root folder | Supported | — |
| Move a file | Not available | Power Automate's Google Drive connector does not offer an equivalent action. |
| Rename a file | Not available | Power Automate's Google Drive connector does not offer an equivalent action. |
| Rename a folder | Not available | Power Automate's Google Drive connector does not offer an equivalent action. |
| Share file link | Not available | Power Automate's Google Drive connector does not offer an equivalent action. |
| Store a file | Not available | Power Automate's Google Drive connector does not offer an equivalent action. |
| Update a file | Supported | — |
Microsoft Exchange Online
6 items
| Action | Status | Notes |
|---|
| Create a calendar item | Supported | — |
| Delete a calendar item | Supported | — |
| Get a calendar item | Supported | — |
| Get calendar items | Supported | — |
| Send email | Supported | — |
| Update a calendar item | Supported | — |
| Action | Status | Notes |
|---|
| Add link to a channel tab | Supported | — |
| Add member to a team | Supported | — |
| Add owner to a team | Supported | — |
| Archive a team | Supported | — |
| Clone a team | Supported | — |
| Create a channel | Supported | — |
| Create a team | Supported | — |
| Get teams | Supported | — |
| List members of a team | Supported | — |
| List owners of a team | Supported | — |
| Post to a channel | Supported | — |
| Remove member from a team | Supported | — |
| Restore archived team | Supported | — |
| Update a team | Supported | — |
OneDrive for Business
10 items
| Action | Status | Notes |
|---|
| Copy a file | Supported | — |
| Create a folder | Supported | Implemented via Create file folder-path workaround. |
| Delete a file | Supported | — |
| Delete a folder | Supported | — |
| Get a file | Supported | — |
| Get file metadata | Supported | — |
| Get folder contents | Supported | — |
| Move a file | Supported | — |
| Share file link | Supported | — |
| Store a file | Supported | — |
SharePoint Online
35 items
| Action | Status | Notes |
|---|
| Add attachment | Supported | — |
| Check in file | Supported | — |
| Check out file | Supported | — |
| Copy file | Supported | — |
| Copy folder | Supported | — |
| Copy or move file (single action) | Planned | Planned: requires deterministic parameter mapping before we can emit reliably. |
| Create document from content type / template-backed create | Supported | Best effort; review generated document metadata after import. |
| Create file | Supported | — |
| Create item | Supported | — |
| Create new document set | Supported | — |
| Create new folder | Supported | — |
| Create sharing link for a file or folder | Supported | — |
| Delete attachment | Supported | — |
| Delete file | Supported | — |
| Delete item | Supported | — |
| Discard check out | Supported | — |
| Get attachments | Supported | — |
| Get file content | Planned | Planned: requires deterministic parameter mapping before we can emit reliably. |
| Get file properties | Supported | — |
| Get files (properties only) | Supported | — |
| Get folder metadata | Planned | Planned: requires deterministic parameter mapping before we can emit reliably. |
| Get item | Supported | — |
| Get items | Supported | — |
| Grant access to an item or a folder | Supported | — |
| List folder | Supported | — |
| Move file | Supported | — |
| Move folder | Supported | — |
| Rename file | Planned | Planned: requires deterministic parameter mapping before we can emit reliably. |
| Rename folder | Planned | Planned: requires deterministic parameter mapping before we can emit reliably. |
| Resolve person | Supported | — |
| Send an HTTP request to SharePoint | Supported | Review method/URI/headers after import. |
| Set content approval status | Supported | — |
| Set item permissions | Planned | Planned: requires deterministic parameter mapping before we can emit reliably. |
| Update file properties | Planned | Planned: requires deterministic parameter mapping before we can emit reliably. |
| Update item | Supported | — |
Word Online (Business)
2 items
| Action | Status | Notes |
|---|
| Convert Word document to PDF | Supported | Review output file path and connector references after import. |
| Populate a Microsoft Word template | Supported | Best effort; assumes template fields align cleanly after import. |
| Action | Status | Notes |
|---|
| Apply to each (For each) | Supported | — |
| Approval outcome branches | Supported | Covers Approved, Rejected, and Returned outcome branching. |
| Assign a task | Supported | Approval semantics may require review after import. |
| Branch by stage | Supported | Emitted as Switch/Scopes; verify stage logic after import. |
| Call a workflow / child workflow | Partial | Requires a child flow or manual wiring depending on tenant strategy. |
| Change stage | Supported | Emitted as variable + Switch/Scopes; verify stage logic after import. |
| Collection operation | Supported | Mapped to array and collection handling such as append and build-list patterns. |
| Commit pending changes (Nintex) | Supported | No direct equivalent; emitted as a no-op Compose for parity. |
| Compose / Expression | Supported | — |
| Condition (If / Else) | Supported | — |
| Delay / Wait | Supported | — |
| Do until (Loop until) | Supported | — |
| Filter / Run if | Supported | Converted to condition and branch logic. |
| Flexi task / multi-outcome approval | Supported | Best-effort conversion to Approval plus outcome branches; review task semantics after import. |
| Initialize variable | Supported | — |
| Log to instance details | Supported | Emitted as Compose (logging placeholder). |
| Math / numeric conversion | Supported | Covers increment, multiply, add-zero coercion, and parse-to-number style actions. |
| Parallel branches | Supported | — |
| Parse / type conversion | Supported | Best effort for common numeric and string coercion patterns. |
| Query user profile (Nintex) | Supported | Converted to Office 365 Users - Get user profile + Set variable. |
| Regular expression | Partial | Complex regex patterns may require manual adjustment after import. |
| Set variable | Supported | — |
| Start approval | Supported | Approval semantics may require review after import. |
| State machine (Nintex) | Supported | Emitted as a Switch/Scopes (best-effort); verify state behavior after import. |
| String building / templating | Partial | Complex templates may require manual edits. |
| Switch | Supported | — |
| Terminate | Supported | — |
| To-do task / Assign to-do task | Supported | Best-effort conversion to Start and wait for an approval; custom Nintex task forms and content types may require follow-up after import. |
| User defined action (Nintex UDA) | Supported | Inlined as a Scope (Option A). |
| Web request / HTTP | Supported | Mapped to Power Automate HTTP; premium connector and auth settings may require review after import. |
How to interpret the statuses
A quick guide to what each status means in practice.
- Supported: Generates an importable package when supported and emits logic directly into the flow definition. Some supported items are best-effort and still deserve connector or semantic review after import.
- Partial: Conversion runs, but you may need to adjust connector-specific settings, rewrite a query, or choose a different target-side replacement after import.
- Planned: Not yet mapped in Flow Migrator, but intended for future support.
- Not available: Power Automate or the target connector does not offer an equivalent action today.