Nintex action decoder

Microsoft Teams - Create a channel

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

Create a channel

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 Create a channel using Microsoft Teams. Maps detected Teams create-channel actions to the native Microsoft Teams Create a channel connector action from the captured Teams template. Validate team, channel name, membership type, and channel policy 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

Open the generated flow and confirm the action card imported correctly.
Validate connection references and required settings before running the flow.
Test with representative source data from the original workflow.

Related action decoder pages

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

Microsoft Teams - Add a member to a channelAdd a member to a channel Microsoft Teams - Remove a member from a channelRemove a member from a channel Microsoft Teams - Add a member to a teamAdd a member to a team Microsoft Teams - Create a teamCreate a team

Want to check your actual workflow?

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

Analyze a workflow