Nintex Workflow Cloud - Get tasks

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 HTTP/API handoff using HTTP / Custom connector. Preserves status/date/workflow-instance filters and the original tasks output object as an importable HTTP handoff. Replace the placeholder token or swap to the customer's NAC API/custom connector before production activation. 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.
• Review HTTP method, URI, headers, authentication, retry behavior, premium licensing, and response parsing.
• Run a test instance and compare outputs against the original Nintex workflow before production migration.

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.