Oracle query / Oracle Execute SQL

What it does

This action reads from, writes to, or queries a database-style data source. The migration depends on the original provider, table or query shape, credentials, gateway requirements, and how returned values are used later in the workflow.

How Flow Migrator maps it

Flow Migrator maps this to Oracle query review placeholder using Oracle Database. Oracle intent is detected and preserved. Native Oracle connector export should be validated with a representative Oracle template before marking supported. 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.
• 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.
5. Confirm gateway connectivity, primary key handling, query filters, and returned data shape.