Component workflow / External start

What it does

This trigger starts a Nintex workflow when the source event occurs. In migration planning, the important details are the original start condition, the source system, and any values the trigger passes into the workflow.

How Flow Migrator maps it

Flow Migrator maps this to HTTP request trigger with typed component inputs using Trigger. Supported component parameters bind from typed root/startData request fields. Endpoint security and caller integration are not automatic; unsupported output/callback/file protocols stop for explicit mapping. 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.
• 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.
• 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.
5. Create a test item/event and verify that the converted flow starts at the expected time.