Nintex action decoder

Microsoft Teams - Add a member to a team

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 a member to a team
Connector
Microsoft Teams
Nintex source
Nintex Automation Cloud
Type
Action

What it does

This action communicates with people or looks up Microsoft 365 user data. Migration review should focus on recipients, dynamic identities, message content, and connector permissions.

How Flow Migrator maps it

Flow Migrator maps this to Add a member to a team using Microsoft Teams. Maps detected Teams add-member-to-team actions to the native Microsoft Teams Add a member to a team connector action from the captured Teams template. Validate user ID/email, owner flag, and team membership permissions after import. Flow Migrator has a direct or proven best-effort conversion path for this mapping.

Common migration issues

  • Confirm recipients, sender behavior, HTML body rendering, attachments, and tenant connector permissions.
  • 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