Reference · built on requestConnectorMessaging & notifications

Mattermost

Teams, channels, posts, and bot accounts on your own Mattermost server through its REST API and WebSocket events.

Request accessPricing ↗

About

Mattermost is a messaging platform that organizations run on their own servers. Every server exposes the same API at your-mattermost-url/api/v4 with JSON bodies, plus a WebSocket at /api/v4/websocket that streams events such as posted, post_edited, reaction_added, and user_added. Fibric connects as a bot account: a service user that cannot log in and authenticates with its own access token. A System Admin creates it and adds it to the teams and channels it may see.

Through Fibric, an operator reads those channels and proposes a post, a reply in a thread, a reaction, or a pin for a person to approve.

This is a reference listing. It documents what Fibric would read from Mattermost and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Posts in a channel through GET /api/v4/channels/{channel_id}/posts and a thread through GET /api/v4/posts/{post_id}/thread
  • Live events over the WebSocket: posted, post_edited, post_deleted, reaction_added, user_added, and channel_created
  • Channels the bot belongs to across teams through GET /api/v4/users/{user_id}/channels
  • Team rosters and channel members through the teams and channels endpoints
  • Search across all teams through POST /api/v4/posts/search
  • Deliveries from outgoing webhooks registered at /api/v4/hooks/outgoing

Proposed actions

  • Target capability: propose a post with POST /api/v4/posts, in a channel or as a reply in a thread
  • Target capability: propose Update a post or Patch a post on a post the bot wrote
  • Target capability: propose a reaction with POST /api/v4/reactions
  • Target capability: propose Pin a post to the channel with POST /api/v4/posts/{post_id}/pin
  • Target capability: propose a message through an incoming webhook created at POST /api/v4/hooks/incoming

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Line-down alerts in the plant channel

    A stoppage from the historian becomes a proposed post in the line's channel with the fault and the last good cycle. The shift lead approves it; a reply in the thread records who is on it.

    With Line Downtime

  • Alarm floods reduced to one pinned post

    When alarms spike, the operator groups them by source and proposes one post with the grouped list, pinned on approval. Acknowledgements collect as replies rather than new posts.

    With Alarm Triage

  • Patch window notices, opening and closing

    Before a maintenance window the operator drafts a notice to the affected teams' channels and a closing post when it ends. Each goes out after a person approves.

    With Patch Window

  • Incident record drafted from the channel

    Posts in an incident channel are read into a draft incident with timestamps and authors. A person edits and files it in the ticketing system.

    With Incident Draft

Requirements

  • A Mattermost server reachable from Fibric at your-mattermost-url/api/v4 over HTTPS
  • A System Admin to set Enable Bot Account Creation to true under System Console, Integrations, Bot Accounts, and create the bot
  • The bot invited into each team and channel it reads or posts in; people add it, it cannot add itself
  • If a personal access token is used instead: Enable Personal Access Tokens turned on under Integration Management
Authentication
A bot account access token, or a personal access token, sent as Authorization: Bearer on every request and used to authenticate the WebSocket.

Limits

  • The server's per-second rate limit is reported in X-Ratelimit-Limit; the documented example allows 10 and answers 429 beyond it
  • Paged endpoints return at most 200 items per page and 60 when per_page is omitted
  • A bot cannot upload files to a channel unless it is also a member of that channel
  • Only System Admins or plugins can create or manage bot accounts

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Mattermost ↗

Questions and answers

Does Fibric need a user login?
No. A bot account is a service account that cannot be logged into and authenticates with a generated access token. A System Admin turns on Enable Bot Account Creation, creates the bot, and adds it to teams and channels. Bots do not count toward an Enterprise Edition user license.
How does Fibric receive new posts?
Over the WebSocket at /api/v4/websocket, authenticated with the same token through an authentication_challenge message. The server then streams events such as posted, post_edited, post_deleted, reaction_added, and typing. Missed events are recovered by reading the channel's posts over REST.
Does this work with a self-hosted server?
Yes. The API is the same wherever the server runs: JSON over HTTPS at your-mattermost-url/api/v4. Fibric needs network reach to that URL, and the server's own rate limit, shown in the X-Ratelimit-Limit header, applies to its requests.
Ask about Mattermost

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Mattermost through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy