ActionMattermostUpdated September 2026

What Mattermost channels exist?

Short answer: You can list mattermost channels in Mattermost by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Mattermost List Mattermost Channels action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

List Mattermost Channels in Mattermost — start free All 7 Mattermost actions

List Mattermost Channels in Mattermost — start free

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.

Triggered by

Apps that pair well as the trigger for List Mattermost Channels.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Mattermost

2 Google Sheets triggers

HubSpot → Mattermost

18 HubSpot triggers

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 run history shows the failed step with its input and the error message Mattermost returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does List Mattermost Channels support batch operations?

Run List Mattermost Channels inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Mattermost's rate limits.

More actions