List Mattermost Channels: Mattermost 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 team_id	string	Required	Team ID. Example: abc123
Per Page per_page	string	Optional	Per Page. e.g. "60"

Sample request

{
  "team_id": "e.g. abc123",
  "per_page": "60"
}

Returns

[
  {
    "id": "chan123",
    "name": "town-square",
    "type": "O",
    "display_name": "Town Square"
  }
]

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

FAQ

Questions about List Mattermost Channels.

What does the List Mattermost Channels action do in Mattermost?

Returns channels in a team that the connected user can see. Useful for channel inventory and for resolving channel IDs at workflow setup.

What inputs does List Mattermost Channels require?

Required: Team ID. 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 Mattermost 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 List Mattermost Channels support batch operations?

Yes. Run List Mattermost Channels inside a Loop node to process arrays. Tiny Command handles Mattermost's rate limits automatically so you don't have to throttle manually.

More actions