Nintex action decoder

Set instance name

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
Compose review/audit step
Connector
Data Operations
Nintex source
Nintex Automation Cloud
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 Compose review/audit step using Data Operations. Power Automate does not expose a native run-name update action, so Flow Migrator preserves the original instance-name expression as an importable Compose step for review/audit. 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.
  • Run a test instance and compare outputs against the original Nintex workflow before production migration.

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