Nintex Workflow Cloud - Get workflow instances

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 HTTP/API handoff using HTTP / Custom connector. Preserves status/date/name/page-size filters and the original instances output object as an importable HTTP handoff. For the legacy NAC API Xtension List workflow instances action, the workflow design ID path parameter is also carried into the generated endpoint. 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 SharePoint site, list/library, content type, required fields, person fields, lookup fields, and attachment or file path 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.