Xtensions custom connector action

What it does

This action calls another service, API, or workflow. The migration must preserve endpoint details, request data, response handling, and any authentication requirements.

How Flow Migrator maps it

Flow Migrator maps this to HTTP/API review scope using HTTP / Custom connector. Preserves connector, operation, request body, and output variables. Replace the placeholder endpoint or swap to a Power Automate custom connector after import. 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.
• 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. 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.