Nintex action decoder

Salesforce record modified trigger

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
When a record is modified
Connector
Salesforce
Nintex source
Nintex Automation Cloud
Type
Trigger

What it does

This trigger starts a Nintex workflow when the source event occurs. In migration planning, the important details are the original start condition, the source system, and any values the trigger passes into the workflow.

How Flow Migrator maps it

Flow Migrator maps this to When a record is modified using Salesforce. Maps Nintex Automation Cloud Salesforce record-modified start events to the native Power Automate Salesforce polling trigger. Validate the Salesforce connection reference, selected object, API access, and trigger cadence after import. 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.
  • Confirm the final trigger type and source binding because trigger semantics often depend on the original workflow context.
  • 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.
  4. Create a test item/event and verify that the converted flow starts at the expected time.

Related action decoder pages

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

Want to check your actual workflow?

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

Analyze a workflow