Create Teams Channel: Microsoft Teams action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Team ID teamId	string	Required	Team ID
Channel Name displayName	string	Required	Channel Name. Example: Project Updates
Description description	string	Optional	Description. e.g. "Channel description"
Type membershipType	options	Optional	Type. Options: Standard, Private, Shared

Sample request

{
  "teamId": "{{trigger.teamId}}",
  "displayName": "e.g. Project Updates",
  "description": "Channel description",
  "membershipType": "{{trigger.membershipType}}"
}

Returns

{
  "id": "19:xyz@thread.tacv2",
  "displayName": "Project Updates",
  "membershipType": "standard"
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Create Teams Channel.

What does the Create Teams Channel action do in Microsoft Teams?

Creates a new channel under a team with name, description, type (standard, private, shared). For "new project → auto-create dedicated channel" workflows.

What inputs does Create Teams Channel require?

Required: Team ID, Channel Name. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Microsoft Teams returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Create Teams Channel support batch operations?

Yes. Run Create Teams Channel inside a Loop node to process arrays. Tiny Command handles Microsoft Teams's rate limits automatically so you don't have to throttle manually.

More actions