Assign a task

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. Maps task title, assigned-to, details, item link, and custom outcomes where detected. Consumed custom fields require an explicit typed separate-capture decision; they are not native approval comments. Commercial Teams capture supports scalar values and text lists; structured people/file fields require a configured replacement-form connector. Capture sends a second request to each original responder and checks identity before continuing. No GCC/GCC High/DoD Flow bot support is assumed. Validate escalations, reminders and notifications after import. Flow Migrator has a direct or proven best-effort conversion path for this mapping.

Common migration issues

• Validate assignees, task outcomes, reminders, escalations, custom task forms, and notification behavior.
• Validate SharePoint site, list/library, content type, required fields, person fields, lookup fields, and attachment or file path behavior.
• Confirm recipients, sender behavior, HTML body rendering, attachments, and tenant connector permissions.

Validation checklist

1. Open the generated flow and confirm the action card imported correctly.
2. Validate connection references and required settings before running the flow.
3. Test with representative source data from the original workflow.
4. Confirm outcome branches and task assignment values match the Nintex behavior.