Send alerts to Mattermost or Rocket.Chat

Create an incoming webhook in Mattermost or Rocket.Chat and post Uptime Tracker down and recovery alerts to a channel. Available on the Pro and Team plans.

Updated By the Uptime Tracker team
  1. Create an incoming webhookMattermost: Integrations, Incoming Webhooks, Add Incoming Webhook. Rocket.Chat: Administration, Workspace, Integrations, New, Incoming.
  2. Pick the channel and saveChoose the channel that should receive alerts and save the webhook.
  3. Copy the webhook URLMattermost URLs look like https://chat.example.com/hooks/<id>; Rocket.Chat URLs like https://chat.example.com/hooks/<id>/<token>.
  4. Add the destinationIn Integrations → Add destination, choose "Set up Mattermost" or "Set up Rocket.Chat", paste the URL and choose "Add destination".
  5. Send a testChoose "Send test" under Configured destinations on Integrations → Destinations.

Mattermost and Rocket.Chat both accept Slack-compatible incoming webhooks, and Uptime Tracker has a destination type for each. They are available on the Pro and Team plans and need no verification step.

Before you start

  • A workspace on Pro or Team.
  • Your chat server must be reachable from the internet over HTTPS, at the root of its host name or under a sub-path (such as https://example.com/mattermost). Servers on private networks are not supported.
  • Permission to create incoming webhooks (an administrator may have to enable them).

Mattermost: create the webhook

  1. Open the product menu and choose Integrations, then Incoming Webhooks.
  2. Choose Add Incoming Webhook, enter a title such as "Uptime Tracker", pick the Channel and save.
  3. Copy the URL. It looks like https://chat.example.com/hooks/xxxxxxxxxxxxxxxxxxxxxxxxxx.

If you cannot find Integrations, a system admin must turn on incoming webhooks in the System Console, under Integrations → Integration Management.

Rocket.Chat: create the webhook

  1. Open Administration, then Workspace → Integrations.
  2. Choose New, then the Incoming tab.
  3. Turn on Enabled, enter a name, set Post to Channel (for example #alerts) and the user to Post as, then save.
  4. Copy the Webhook URL. It looks like https://chat.example.com/hooks/<id>/<token>.

Add it in Uptime Tracker

  1. Go to Integrations → Add destination and choose Set up Mattermost or Set up Rocket.Chat.
  2. Enter a Name and paste the Mattermost incoming webhook URL or Rocket.Chat webhook URL.
  3. Choose Add destination, then Send test.

Messages show the alert title, the time, a Reason: line on down alerts (for example HTTP 503 Service Unavailable) and the redacted target.

Change the webhook

To move alerts to another channel or server, create the new incoming webhook, then choose Edit connection on the destination, paste the new URL and choose Save connection. Saving also re-enables a destination that was disabled after delivery failures.

Acknowledge from the chat

  • Mattermost: alerts for open incidents have an Acknowledge button. The first time you press it, a link only you can see asks you to link your Mattermost account (once per Mattermost server) to your Uptime Tracker sign-in. After that, a press acknowledges the incident as you; the post is rewritten without the button. Buttons work for 30 days after the alert, and your Mattermost server must be able to reach uptimetracker.live over the internet.
  • Rocket.Chat: webhook messages cannot call back into Uptime Tracker, so the Acknowledge button opens a page where you sign in and confirm.

Troubleshooting

  • "The endpoint is not a valid mattermost URL" (or rocketchat): the URL must use HTTPS and end in /hooks/<id> for Mattermost or /hooks/<id>/<token> for Rocket.Chat. A sub-path of up to 5 segments may come before /hooks; query strings, .. segments and percent-encoded characters are refused.
  • "Destination must be a publicly routable HTTPS endpoint": the host resolves to a private address or does not serve HTTPS.
  • Integrations → Deliveries shows an error code: when the server answers with a Slack-style error code, it is shown after the status, for example destination returned HTTP 404 (channel_not_found) or (channel_is_archived). Fix the channel, or point the webhook at another one.
  • HTTP 401, 403 or 404 under Integrations → Deliveries: the webhook was deleted or disabled. The destination is disabled with a reason; create a new webhook and paste it with Edit connection.
FAQ

Frequently asked questions

Can I use the Slack destination for Mattermost?

No. The Slack destination only accepts hooks.slack.com URLs. Use the Mattermost or Rocket.Chat destination type instead.

Which plan do I need?

Pro or Team.

Does my chat server need to be public?

Yes. Uptime Tracker only delivers to publicly reachable HTTPS endpoints, never to private network addresses. Servers under a sub-path, such as https://example.com/chat, are supported.

Uptime Tracker

Start monitoring in under five minutes

Start on the free plan — commercial use allowed. No credit card required.

  • Free forever plan
  • No credit card
  • Cancel anytime