Nintex action decoder

Add attachment to an item

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
Add attachment
Connector
SharePoint
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 Add attachment using SharePoint. Maps to SharePoint Add attachment. For task-form attachment loops, validate the generated file name and file content expressions during UAT. Flow Migrator has a direct or proven best-effort conversion path for this mapping.

Common migration issues

  • Validate assignees, task outcomes, reminders, escalations, custom task forms, and notification behavior.
  • 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.

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. Confirm site/list/library names and complex field mappings in the target tenant.

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