Start workflow / Call a workflow

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 Mapped HTTP child workflow invocation using Power Automate / HTTP. Required settings maps a separately migrated child to its signed HTTP trigger and typed request/response properties. Waited calls preserve completion semantics with HTTP 200 and asynchronous polling; concurrent calls require HTTP 202 acceptance without polling. Outputs are validated before assignment. Automatic child discovery/deployment is not implemented; a URL alone is insufficient without the verified child contract. 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.
• Confirm the final trigger type and source binding because trigger semantics often depend on the original workflow context.

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.