Slack, Teams & chat apps

SutramX posts incident alerts and notices straight into your team chat. Slack, Microsoft Teams, Discord, Google Chat, Mattermost and Telegram are included on every plan. Each one takes a minute to connect.

All chat channels are managed on Alerts → Channels & API, on the Integrations tab. Only the workspace owner can connect, edit or disconnect them; any member who can make changes can send a test.

What chat channels receive#

Quick connect with a pasted link#

If you already have a webhook link, paste it into the box under Already have a webhook link? at the top of the Integrations tab. SutramX recognises Slack, Discord, Microsoft Teams, Google Chat, Mattermost and Zapier links and connects the right channel. A link it doesn't recognise can be connected as a custom webhook with Connect as a webhook. Zapier and custom webhooks depend on your plan.

Slack#

Connect with Slack (one click)#

If the Slack card shows Connect with Slack:

1. Click Connect with Slack.
2. Sign in to Slack, pick the channel for alerts and approve.
3. You return to SutramX with the connection added and a test message posted.

One-click Slack connections add an Acknowledge button to down alerts. Clicking it acknowledges the incident in SutramX, stops its escalation, and replaces the button with "Acknowledged by @name — escalation stopped."

Connect with an incoming webhook#

If the card shows Connect Slack (or you choose Enter a webhook URL manually):

1. Open api.slack.com/apps and choose Create New App → From scratch.
2. Enable Incoming Webhooks and click Add New Webhook to Workspace.
3. Pick the channel and copy the webhook URL. It starts with https://hooks.slack.com/.
4. In SutramX, click Connect Slack, paste it into Link from Slack, and click Connect.

Alerts posted through a pasted webhook have no Acknowledge button.

Microsoft Teams#

Teams alerts arrive as Adaptive Cards through a Teams Workflows webhook.

1. In Teams, open the channel, click ⋯ (More options) → Workflows, and choose Send webhook alerts to a channel.
2. Click through the wizard and copy the link it shows at the end.
3. In SutramX, click Connect Microsoft Teams, paste it into Link from Teams, and click Connect.

Teams accepts a request before it posts the card, so a successful test says "Teams accepted the test card — check the channel to confirm it arrived". Look in the channel to be sure.

Discord#

1. In Discord, open the channel's settings and go to Integrations → Webhooks → New Webhook.
2. Copy the webhook URL. It starts with https://discord.com/api/webhooks/.
3. In SutramX, click Connect Discord, paste it into Link from Discord, and click Connect.

If the card offers Connect with Discord, you can instead sign in to Discord and pick the channel. Alerts are posted with the SutramX avatar, and @everyone, @here and role mentions in monitor names are never triggered.

Google Chat#

You need a Google Workspace account; personal Gmail accounts can't create webhooks.

1. Open the space, click the space name at the top, then Apps & integrations → Webhooks → Add webhooks.
2. Name it "SutramX", save, and copy the webhook URL. It starts with https://chat.googleapis.com/v1/spaces/.
3. In SutramX, click Connect Google Chat, paste it into Link from Google Chat, and click Connect.

Mattermost#

Your Mattermost server must be reachable from the internet.

1. In Mattermost, open Main menu → Integrations → Incoming Webhooks → Add Incoming Webhook. An admin may need to enable incoming webhooks first.
2. Pick the channel, save, and copy the URL. It ends in /hooks/ and an ID.
3. In SutramX, click Connect Mattermost, paste it into Link from Mattermost, and click Connect.

Posts appear with the username SutramX, and @channel, @all and @here in monitor names never fire a mention.

Telegram#

Telegram alerts come from the SutramX bot. You don't create a bot or paste a token. Each chat or group you link becomes its own connection.

Private chat#

1. On the Telegram card, click Connect with Telegram.
2. Telegram opens a chat with the SutramX bot. Press Start.
3. The chat is linked automatically and added as a new Telegram connection.

Group#

1. Click Add to a group.
2. Pick the group in Telegram and add the bot to it.
3. The group is linked automatically.

Each link works once and expires after 30 minutes. If it expires, click Get a new link.

Channel#

1. Click Add to a channel. SutramX shows a message that starts with /start followed by a one-time code.
2. Add the SutramX bot to the channel as an admin that can post messages.
3. Post that message in the channel. The channel is linked automatically.

The code works once and expires after 30 minutes.

Re-adding a chat by ID#

The SutramX bot only sends to chats that were linked to your workspace through one of the steps above. Re-add a linked chat by ID reconnects such a chat, for example after you disconnected it. A chat ID that was never linked is refused.

If a Telegram group is upgraded to a supergroup, SutramX updates the stored chat ID automatically. To move alerts to a different chat, link the new one and disconnect the old one.

Routing and multiple channels#

You can connect up to 10 connections per chat app, for example one Slack channel per team. Each connection has its own routing:

1. Open the connection's menu and choose Routing.
2. Pick All monitors, Selected groups or Selected monitors.
3. Select the groups or monitors and click Save routing.

SSL, domain and maintenance notices follow the same routing: a connection routed to selected monitors only gets notices that concern those monitors. Website health, third-party and ISP outage notices go to every connection. Escalation steps ignore routing and post to every connection of the targeted chat app.

Testing a connection#

Slack, Teams, Discord, Google Chat and Mattermost connections are tested automatically right after you connect. A Telegram chat linked through the bot gets a "Connected to SutramX" message from the bot instead. To test again, open the connection's menu and choose Send test.

A test posts a down alert for a monitor called "SutramX test alert", with the detail "This is a test message for your Slack integration. No action needed." (with the app's name). If the test fails, the card shows the provider's error and offers Retry test.

Message format#

Slack, Discord, Google Chat and Mattermost receive plain text:

[DOWN] Checkout API is DOWN
URL: https://api.example.com/health
Region: FRA1 (Frankfurt, Germany)
Detail: <failure reason>
Why: Down from 2 of 3 regions: HTTP 503 server error (Arizona still up)
Details: https://app.sutramx.com/dashboard/incidents/<incident id>

[UP] Checkout API has RECOVERED
URL: https://api.example.com/health
Downtime: 4m 12s
Details: https://app.sutramx.com/dashboard/incidents/<incident id>

The Why line is the incident's one-line verdict, included on down alerts when one is available. See Why this alert & flakiness score.

If someone resolves the incident by hand, the message is [RESOLVED] Checkout API: incident resolved manually, with how long the incident was open and a note that the monitor hasn't been confirmed back up.

Microsoft Teams gets an Adaptive Card with the same lines: a red [DOWN] or green [UP] title, URL, region, downtime or detail, the Why line, and a View incident button.

Telegram gets a formatted message with DOWN, RECOVERED or RESOLVED MANUALLY, the monitor name, URL, region, the time the outage started (in UTC), the reason and Why line or the downtime, and a View incident link.

Notices start with a tag such as [SSL], [DOMAIN], [MAINTENANCE], [SITE HEALTH], [THIRD-PARTY], [ISP OUTAGE] or [ISP RECOVERED], followed by a headline, a few detail lines and a link. For example:

[SSL] SSL certificate for Checkout API expires in 7 days
Monitor: Checkout API
URL: https://api.example.com/health
Expires: 2026-10-09
Reminder: 7 days before expiry
Details: https://app.sutramx.com/dashboard/<monitor id>

Monitor names, URLs and failure reasons are escaped for each app, so they can't create links, mentions or formatting. Very long messages are shortened to fit each app's limit.

Editing and disconnecting#

From a connection's menu:

Webhook links work like passwords: anyone who has one can post to your channel. SutramX stores them encrypted and only shows the start and last characters. If a link leaks, delete the webhook in the chat app and connect a new one.

Troubleshooting#

• "This doesn't look like a Slack webhook URL": the link is for a different service, or incomplete. Copy the full URL again from the app.
• "Office 365 connectors were retired by Microsoft": create a Workflows webhook as described in Microsoft Teams.
• "This address isn't reachable from the internet": SutramX can only post to public HTTPS addresses. For Mattermost, expose the server's webhook endpoint publicly.
• "Endpoint redirected to …": paste the final URL, not one that redirects. SutramX doesn't follow redirects.
• Connection shows Failing: the last 3 deliveries failed. Common causes are a deleted webhook, an archived channel or a bot removed from a Telegram chat. Fix it, then use Send test.
• Temporary errors: if the app is rate limiting or briefly down, SutramX retries automatically for a few minutes and honours the app's requested wait time. Errors the app reports as permanent (for example a deleted webhook) aren't retried.