Flexi task / Request approval

What it does

This Nintex action creates or coordinates human work, such as an approval, review, or task record. It usually controls who receives work, what details they see, and which branch the workflow follows after the response.

How Flow Migrator maps it

Flow Migrator maps this to Start and wait for an approval using Approvals. Approval can be generated, but lazy approval, custom task forms, reminders, escalations, and branch semantics should be reviewed. 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 assignees, task outcomes, reminders, escalations, custom task forms, and notification behavior.
• Check converted expressions, branch ordering, loop exit conditions, and state-machine transitions.

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 outcome branches and task assignment values match the Nintex behavior.