List Channels
teams.list_channels
ActionChat & messagingconnection required
GET /teams/{id}/channels, following @odata.nextLink.
Channels in a team — where a channel_id comes from.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Microsoft Teams
- Secret shape
- {"client_id", "client_secret", "refresh_token"}
- Config it needs
- tenant
- Resolved by
- config.connection_id, else node.connection_id
Configuration
2 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
team_id Team (group) id. | string | Yes | — | — | — |
max_results Budget across pages, not a page size. | number | No | — | ≥ 1 | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
channels Each: id, name, description, membership_type, web_url. | array | — |
count | number | — |
{
"channels": [],
"count": 0
}Notes
- Needs a delegated Channel.ReadBasic.All permission.
Related Microsoft Teams nodes
Templates that use Microsoft Teams
Solutions with Microsoft Teams
See List Channels run in a workflow.
In a technical demo we add the Microsoft Teams connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.