Recent supported action coverage updates
The compatibility matrix should track reusable action families, not one-off workflow display names. Recent converter work added support for several underlying Nintex action types that appear across customer workflows. Use this article as a release-note style summary before checking the full compatibility matrix or action decoder pages.
How to read these updates
Support is added by normalized action family. That means a workflow step named Update Account Emails and another step named Set Case Status can share the same converter template if both use the same underlying Salesforce update_record operation.
The compatibility matrix should list the action family and target mapping. Individual workflow display names should not create separate matrix rows unless they represent a different underlying Nintex action type.
Salesforce action families now covered
- Salesforce create_record maps to Salesforce - Create record.
- Salesforce update_record maps to Salesforce - Update record (V3).
- Salesforce store_file maps to ContentVersion creation and reads back ContentDocumentId for downstream linking.
- Salesforce associate_file_to_record maps to ContentDocumentLink creation.
- Salesforce add_attachments_to_record loops over the detected file collection and creates ContentVersion records linked to the target record.
People, workflow, API, and table actions now covered
- Query user profile maps to Office 365 Users - Get user profile (V2) and preserves a Nintex-compatible profile object.
- Get manager maps to Office 365 Users - Get manager (V2).
- Azure Active Directory Query users maps to Office 365 Users - Search for users (V2) plus output shaping.
- Start workflow is exported as an HTTP child-flow handoff that preserves target workflow ID, inputs, execution timing, and waited outputs.
- Nintex Workflow Cloud Get tasks and Get workflow instances are exported as importable HTTP/API handoffs that preserve filters and output shape.
- Nintex Tables Query rows, Create row, and Update row are exported as importable HTTP/API handoffs for the customer-approved Nintex Tables API or custom connector.
- Broadway Core API Get By CIF, Get Accounts, and Get Account Details are exported as custom HTTP/API handoffs with request and output wiring preserved.
Data operation coverage added
- Regular expression supports common extract, split, and replace patterns.
- Modify string supports common replace, substring, insert, remove, length, and index operations.
- Convert value maps common type conversions such as int, float, bool, string, and date formatting.
- Count items in collection maps to length() over the detected collection.
- Add item to collection, Clear collection, Join items in collection, and Remove duplicates from collection map to array variable or expression patterns.
- Convert string to uppercase maps to toUpper().
- Date interval and custom DateTime formatter patterns map to Power Automate date/time expressions.
- Terminate workflow instance maps to Power Automate Terminate when the source targets the current workflow instance.
What still needs explicit UAT
Supported does not remove UAT. It means the converter has a deterministic target pattern and should not block export as unsupported. Several new patterns, especially SharePoint REST, Salesforce files, Nintex Tables, and custom API handoffs, are intentionally importable but still require tenant-specific connection, permission, token, endpoint, and data-shape validation.
For customer communication, call out placeholders clearly: HTTP/API handoffs must be replaced with the approved endpoint, token, child flow URL, or custom connector before production activation.

