Post a confirmed outage
The message goes out once enough independent EU locations fail the check often enough in a row, both thresholds sit in your package, not on the first failed request.
Use Uptimeify with Mattermost.
One incoming webhook on your own server, and every confirmed outage lands in the channel your team already watches. Nothing leaves your chat.
What lands in Mattermost
Everything the alert pipeline sends into Mattermost is on this list, and nothing beyond it. Read it once and you know what your team will see.
Post the recovery
The same channel gets the all clear as soon as the check is green again, under its own heading rather than as another alarm.
Speak the Slack compatible payload
The incoming webhook receives the same shape it takes from Slack, so the integration you already know how to create is the one that works.
Say what actually broke
Site, URL, the error in plain language, incident type, status code, response time and the checking locations follow the heading.
Reach your own server
Any https host is accepted, since Mattermost is yours to run, and the address is checked against internal targets before it is called.
Warn before certificates and domains expire
Expiring TLS certificates, expiring domains and blocklist hits reach the same channel, early enough to act without a rush.
A channel per monitor
Each channel is its own webhook, so a client's outage reaches the people who look after that client instead of everyone.
Send a test message
The dashboard posts a test into the channel while you set it up, so the first real alert is not the first delivery attempt.
Keep the webhook URL out of sight
The URL carries the token, so it is stored encrypted and shortened to its origin before the attempt shows up under History & Logs → Alerts.
Teams that run their monitoring on Uptimeify
Minutes to set up. Then it runs on its own.
1. Open the integrations menu
In Mattermost open the main menu, then Integrations, then Incoming Webhooks, and add one.
Webhook URL
mattermost.yourcompany.com/hooks/xxxxStored encrypted
2. Pick the channel
Choose the channel the alerts should land in and copy the webhook URL your server generates.
3. Paste it into Uptimeify
Add the URL as a Mattermost channel, assign the monitors it covers, and send the test message.
Before you connect Mattermost.
That is the case it is built for. Any https host is accepted, and the address is resolved and checked against internal and loopback targets before a request is sent, so a webhook URL cannot be pointed inward.
No. An incoming webhook created in the integrations menu is enough, and Uptimeify only ever posts to it.
Yes. Every channel is its own webhook, and you assign monitors and clients to it. A client's outage then reaches the people who look after that client, not everyone.
No. Your quota covers monitors and the monthly SMS and voice allowance. Alerts over Mattermost, email, webhook or Slack do not draw on it.
The attempt shows up under History & Logs → Alerts with the status code your server returned, and a hanging endpoint is cut off after fifteen seconds so it cannot stall the alerts queued behind it.
Every alert, where your team already works.
Connect Mattermost once, and every confirmed outage reaches the channel on your own server.