Nintex action decoder

Salesforce Add attachments to a 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
Apply to each file + Create ContentVersion with FirstPublishLocationId
Connector
Salesforce
Nintex source
Nintex Automation Cloud
Type
Action

What it does

This action works with SharePoint list items, files, folders, metadata, content approval, or permissions. The key migration inputs are the target site, list or library, field mappings, and any dynamic item identifiers.

How Flow Migrator maps it

Flow Migrator maps this to Apply to each file + Create ContentVersion with FirstPublishLocationId using Salesforce. Supported for Nintex Automation Cloud Salesforce add-attachments-to-record Xtension actions. Emits a loop over the detected file collection and creates Salesforce ContentVersion records linked to the target record through FirstPublishLocationId. Validate file content shape, Salesforce Files permissions, and file-size limits in UAT. Flow Migrator has a direct or proven best-effort conversion path for this mapping.

Common migration issues

  • Validate SharePoint site, list/library, content type, required fields, person fields, lookup fields, and attachment or file path behavior.
  • Check converted expressions, branch ordering, loop exit conditions, and state-machine transitions.
  • 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.

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