Post a confirmed outage
The message goes out once enough independent EU locations fail the check often enough in a row, not on the first failed request; both thresholds sit in your package.
Use Uptimeify with Google Chat.
One incoming webhook in the space, and every confirmed outage arrives where your team already coordinates. No second tool to check.
What lands in Google Chat
Everything the alert pipeline sends into Google Chat is on this list, and nothing beyond it. Read it once and you know what your team will see.
Post the recovery
The same space gets the all clear as soon as the check is green again, under its own heading rather than as another alarm.
Keep the message plain
Every event is one plain text message with an emoji heading, because bold syntax differs between chat tools and plain text renders right in all of them.
Say what actually broke
Site, URL, the error in plain language, incident type, status code, response time and the checking locations follow the heading.
Accept only the Google host
The webhook has to be a chat.googleapis.com address, so a mistyped or internal URL is refused before any request leaves.
Warn before certificates and domains expire
Expiring TLS certificates, expiring domains and blocklist hits reach the same space, early enough to act without a rush.
A space 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 space 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 key, 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 space
In Google Chat open the space the alerts should land in, then Apps and integrations, then Webhooks.
Webhook URL
chat.googleapis.com/v1/spaces/AAAA/messagesStored encrypted
2. Create the webhook
Add a webhook, give it a name your team recognises, and copy the URL Google Chat generates.
3. Paste it into Uptimeify
Add the URL as a Google Chat channel, assign the monitors it covers, and send the test message.
Before you connect Google Chat.
Only a chat.googleapis.com address. Anything else is refused when the channel is saved, which is what keeps a mistyped host or an internal address from ever being called.
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.
Because bold and code syntax differ between chat tools, and a message that renders correctly in one of them renders as raw characters in the next. Plain text with an emoji heading reads right everywhere.
No. Your quota covers monitors and the monthly SMS and voice allowance. Alerts over Google Chat, email, webhook or Slack do not draw on it.
The attempt shows up under History & Logs → Alerts with the status code Google 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 Google Chat once, and every confirmed outage reaches the space that is already open.