Nintex action decoder

Broadway Core API - Get By CIF / Get Accounts / Get Account Details

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

HTTP/API handoff scope

Connector

HTTP / Custom connector

Nintex source

Nintex Automation Cloud

Type

Action

What it does

This action calls another service, API, or workflow. The migration must preserve endpoint details, request data, response handling, and any authentication requirements.

How Flow Migrator maps it

Flow Migrator maps this to HTTP/API handoff scope using HTTP / Custom connector. Preserves the custom Xtension operation, request body, and output variable as an importable HTTP handoff. Replace the placeholder endpoint with the customer's final Broadway Core API endpoint or Power Automate custom connector before production activation. Flow Migrator has a direct or proven best-effort conversion path for this mapping.

Common migration issues

Review HTTP method, URI, headers, authentication, retry behavior, premium licensing, and response parsing.
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.

Related action decoder pages

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

Xtensions custom connector actionHTTP/API handoff scope Nintex Tables - Create rowCreate row HTTP/API handoff Nintex Tables - Query recordsQuery rows HTTP/API handoff Nintex Tables - Update rowUpdate row HTTP/API handoff

Want to check your actual workflow?

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

Analyze a workflow