Set workflow status (Nintex for SharePoint)

What it does

This action works with SharePoint list items, files, folders, metadata, content approval, or permissions. The key migration inputs are the target site, list or library, field mappings, and any dynamic item identifiers.

How Flow Migrator maps it

Flow Migrator maps this to Update item - WorkflowStatus text column using SharePoint. Preserves the saved status text in an existing ordinary WorkflowStatus Text column on the current list item. Does not change Power Automate run status or recreate the legacy workflow status page/column. Source metadata must identify that text column; absent/ambiguous targets and site workflows block export. Confirm the destination column and bindings before activation. 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 SharePoint site, list/library, content type, required fields, person fields, lookup fields, and attachment or file path behavior.
• 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.
5. Confirm site/list/library names and complex field mappings in the target tenant.