Nintex action decoder

Query XML with XSLT transform

What this Nintex action does, how Flow Migrator maps it to Power Automate, and what to check during migration.

Support level
Partial

Flow Migrator can preserve and generate the core mapping, but this action should be reviewed after import.

Power Automate target
XSLT/HTML transform review placeholder
Connector
Data Operations / HTTP
Nintex source
Nintex cloud and SharePoint workflows
Type
Action

What it does

This action transforms, extracts, or stores data used by later workflow steps. The converted flow must preserve the source expression, output variable, and any formatting or type conversion behavior.

How Flow Migrator maps it

Flow Migrator maps this to XSLT/HTML transform review placeholder using Data Operations / HTTP. XSLT has no clean native Power Automate equivalent. The transform details are preserved for manual HTML construction, HTTP, or Azure Function replacement. Flow Migrator can preserve and generate the core mapping, but this action should be reviewed after import.

Common migration issues

  • Review the generated action after import because some Nintex behavior does not map one-to-one to Power Automate.
  • Validate expression syntax, data types, escaping, HTML output, and array/object handling in Power Automate.
  • Review HTTP method, URI, headers, authentication, retry behavior, premium licensing, and response parsing.

Validation checklist

  1. Review this item before export or immediately after import.
  2. Open the generated flow and confirm the action card imported correctly.
  3. Validate connection references and required settings before running the flow.
  4. Test with representative source data from the original workflow.

Related action decoder pages

Review nearby mappings that often appear in the same Nintex workflows.

Want to check your actual workflow?

Upload a Nintex export to see which actions are supported, partial, or need manual review.

Analyze a workflow