The flow
Starts it 1Service 19
The steps in the order they run, from what starts it.
- 1Add a user to a channelMattermost ToolService
- 2Create a channelMattermost ToolService
- 3Delete a channelMattermost ToolService
- 4Get a page of members for a channelMattermost ToolService
- 5Restore a soft-deleted channelMattermost ToolService
- 6Search for a channelMattermost ToolService
- 7Get statistics for a channelMattermost ToolService
- 8Delete a messageMattermost ToolService
- 9Post a messageMattermost ToolService
- 10Post an ephemeral messageMattermost ToolService
- 11Create a reactionMattermost ToolService
- 12Delete a reactionMattermost ToolService
- 13Get many reactionsMattermost ToolService
- 14Create a userMattermost ToolService
- 15Deactivate a userMattermost ToolService
- 16Get a user by emailMattermost ToolService
- 17Get a user by IDMattermost ToolService
- 18Get many usersMattermost ToolService
- 19Invite a userMattermost ToolService
- 20Mattermost Tool MCP ServerMcp triggerStarts it
How it's built
- Starts on
- An event in a connected app
- Steps
- 20
- Size
- Medium: a working afternoon
- Connects to
- Nothing by connector; it calls services over plain HTTP
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account. You connect your own accounts after importing it; none are included.
What starts it?
It starts on an event in a connected app.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Plan an afternoon. 20 steps is enough that you should read each one before running it.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Before you run itNothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 20 steps before you point it at anything that matters.