Query JSON

What it does

This action transforms, extracts, or stores data used by later workflow steps. The converted flow must preserve the source expression, output variable, and any formatting or type conversion behavior.

How Flow Migrator maps it

Flow Migrator maps this to Expression / Parse JSON / Set variable using Data Operations. Converts rooted or root-relative property/index paths, array wildcards, quoted field unions, named descendants with further selectors, and recursive member-existence filters joined by &&. Native bounded parsing retains ordered first/all matches, duplicates and nulls. Other predicates and dynamic/script selectors require an explicit implementation. Recursive scanning fails rather than publishing partial results when its limit is reached. Validate representative payloads and request consumption in the target tenant. Flow Migrator has a direct or proven best-effort conversion path for this mapping.

Common migration issues

• Validate expression syntax, data types, escaping, HTML output, and array/object handling in Power Automate.
• 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.