Mattermost alerts from AlertHub incoming webhooks

Mattermost alerts from AlertHub incoming webhooks

Self-hosted and Mattermost Cloud teams already live in channels, not Slack. The usual trap is one incoming webhook per SaaS, then a graveyard of /hooks/ URLs when someone rotates the channel.

AlertHub treats Mattermost like Discord or Teams: you paste one incoming webhook on the project. Sources stay on https://api.thealerthub.com/sendAlert (or email ingest). AlertHub detects Mattermost (mattermost) and posts an attachment with project, level, title, and description.

Docs: Mattermost destination.

How Mattermost delivery works

  1. In Mattermost: enable Incoming Webhooks in System Console, then Integrations → Incoming Webhooks → Add Incoming Webhook. Copy the URL (https://your-server/hooks/...).
  2. In AlertHub: project Connections → Webhooks → paste the URL.
  3. Warning and critical alerts become Mattermost attachments (red for critical, amber for warning). Info stays in the dashboard.

Works on Mattermost Cloud (*.cloud.mattermost.com) and self-hosted, including a subpath install (example.com/mattermost/hooks/...).

Setup (once)

  1. Create a project at app.thealerthub.com.
  2. Create the incoming webhook on the ops channel (not a customer-facing one).
  3. Paste it in AlertHub and send a test warning via the Ingestion API.

Alert 1: Self-hosted on-call

Ops already lives in Mattermost. Put Stripe failures, uptime, and GitHub Actions on the same AlertHub project so Mattermost is the only extra destination to add.

Alert 2: Mattermost + email destination

AlertHub also has an email destination for people who mute channels. Same sources; Mattermost for the channel, email for the auditor.

Alert 3: Migrate off per-app Mattermost webhooks

When each vendor has its own /hooks/ URL, rotating the channel means touching Stripe, Shopify, and CI. Move ingest to AlertHub (Shopify, email ingest), then keep a single Mattermost URL in Connections.

Ideas to squeeze more value

  • Channels vs DMs. Incoming webhooks post to a channel. For a personal ping, prefer Telegram, WhatsApp Pro, or mobile push.
  • Do not mix customers into the ops channel. PII in order emails is easier to overshare in Mattermost than in a private Telegram.
  • Same pattern as Slack. If a second team still uses Slack, add the Slack destination on the same project.

FAQ

Is Mattermost a first-class destination?
Yes. AlertHub formats attachments when the stored webhook is classified as Mattermost, same family as Discord and Teams.

Does it work with self-hosted Mattermost?
Yes. Paste the Incoming Webhook URL from your server. AlertHub matches /hooks/{id} on any host.

Do info alerts appear in the channel?
No. Raise the source level when the channel should see it.

Next steps

Paste a Mattermost webhook in Connections, follow the Mattermost setup, and send one test warning.

Related: Discord embeds · Microsoft Teams alerts