Nintex action decoder

Get SQL record

What this Nintex action does, how Flow Migrator maps it to Power Automate, and what to check during migration.

Support level

Supported

Flow Migrator has a direct or proven best-effort conversion path for this mapping.

Power Automate target

Get row (V2)

Connector

SQL Server

Nintex source

Nintex cloud and SharePoint workflows

Type

Action

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 Get row (V2) using SQL Server. Maps single-record SQL Server lookups to Get row when a primary key value is available. Flow Migrator has a direct or proven best-effort conversion path for this mapping.

Common migration issues

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

Open the generated flow and confirm the action card imported correctly.
Validate connection references and required settings before running the flow.
Test with representative source data from the original workflow.
Confirm gateway connectivity, primary key handling, query filters, and returned data shape.

Related action decoder pages

Review nearby mappings that often appear in the same Nintex workflows.

Create SQL recordInsert row (V2)Delete SQL record(s)Delete row (V2), sometimes with Get rows + Apply to each Query SQL table / Execute SQL selectGet rows (V2)Update SQL record(s)Update row (V2), sometimes with Get rows + Apply to each

Want to check your actual workflow?

Upload a Nintex export to see which actions are supported, partial, or need manual review.

Analyze a workflow