SQL Server item modified trigger

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 When an item is modified (V2) using SQL Server. Uses the SQL Server V2 trigger template. Validate gateway, table, rowversion column, and connection reference. 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.
• Confirm connection references, gateway setup, server/database names, table names, primary keys, credentials, and returned result shape.
• 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. Confirm gateway connectivity, primary key handling, query filters, and returned data shape.
6. Create a test item/event and verify that the converted flow starts at the expected time.