Create an incoming webhook
- In Mattermost, open the main menu → Integrations → Incoming Webhooks → Add Incoming Webhook. If you do not see it, ask an admin to enable incoming webhooks.
- Pick the channel, give it a name such as "SutramX", and save.
- Copy the URL. It ends in /hooks/ followed by a code.
Then click Connect Mattermost on the Mattermost card in SutramX, paste the URL into "Link from Mattermost" and click Connect. A test message is posted straight away.
SutramX sends alerts from the internet, so your Mattermost server must be reachable from it. Addresses on a private network are blocked for security.
What the alert looks like
Posts appear with the username SutramX, as plain text: a [DOWN] or [UP] tag with the monitor name, the URL, the region that confirmed the failure, the failure detail or the total downtime, and a link to the incident.
[DOWN] Checkout API is DOWN
URL: https://api.example.com/health
Region: FRA1 (Frankfurt, Germany)
Detail: <failure reason>
Details: <link to the incident in SutramX>
[UP] Checkout API has RECOVERED
URL: https://api.example.com/health
Downtime: 4m 12s
Details: <link to the incident in SutramX>Monitor names, URLs and failure reasons are escaped, so @channel, @all and @here inside a monitor name never fire a mention. The channel also gets notices tagged [SSL], [DOMAIN], [MAINTENANCE], [SITE HEALTH] or [THIRD-PARTY] for expiry reminders, maintenance windows, website health changes and third-party providers you follow.
Reaching a self-hosted server
Mattermost Cloud works as it is. For a self-hosted server, the webhook URL must resolve to a public address and answer over HTTPS. If the server sits behind a VPN or on an internal network, expose only the /hooks/ path through your reverse proxy, and keep the rest of the server private if you prefer. SutramX does not follow redirects, so give it the final URL your proxy serves, not one that redirects to it.
Troubleshooting
- "This address isn't reachable from the internet": the URL points at a private, loopback or internal address. Expose the webhook endpoint publicly as described above.
- "Endpoint redirected to …": you pasted an address that redirects (for example http:// to https://, or a short domain to the real one). Paste the final URL.
- Incoming Webhooks is missing from the Integrations menu: a system admin needs to enable incoming webhooks in the System Console, and may need to let non-admins create them.
- The connection shows Failing: the last 3 deliveries failed and the workspace owner was emailed. Check that the webhook still exists and the channel has not been archived, then use Send test.
- Your server is restarting or overloaded: SutramX retries temporary errors for a few minutes before giving up.
Routing and escalation
Each incoming webhook posts into the channel you chose when you created it. Connect up to 10 Mattermost webhooks and give each its own routing, so the database team's channel only hears about database monitors. Notices follow the same routing. With escalation policies (on Growth and Pro), a Mattermost step posts to every Mattermost connection, ignoring routing, with the detail "Escalation step 2: still down".
Common questions
Does SutramX need a Mattermost bot account?
No. An incoming webhook is enough. Posts show the username SutramX.
Can I acknowledge an incident from Mattermost?
Not from the post. Follow the incident link and acknowledge it on the incident page, which stops any escalation.
Is the webhook URL kept secret?
SutramX stores it encrypted and only shows its start and last characters. Anyone who has the URL can post to the channel, so if it leaks, delete the webhook in Mattermost and connect a new one.
Connect it in SutramX
- Sign in to the SutramX dashboard and open Integrations & API in the sidebar, then the Integrations tab.
- On the Mattermost card, click Connect. Where you see "Connect with …", you just sign in and approve. Otherwise the card shows two or three short steps and one box to paste into.
- Already have a webhook link? Paste it into the box at the top of the page and SutramX works out which service it belongs to.
- SutramX sends a test straight away so you can confirm delivery before any real incident.
- Optional: use Routing to send only some monitors or groups to this channel.
You can connect more than one Mattermost destination. Each connection has its own routing, so different channels can receive different monitors.
All plans, Free included. Compare plans on the pricing page, or see all integrations.
Other chat integrations
- Microsoft Teams alerts setup: Post Adaptive Card alerts to a channel through a Teams Workflow.
- Telegram alerts setup: Alerts from the SutramX bot in a private chat, group or channel.
Related reading
- Features: Alerting & Escalation
- Guides: Reducing False Alerts, Incident Response Basics and On-Call Rotation
- Use cases: Monitoring for Developers & Indie Hackers
- Documentation: Slack, Teams & chat apps