Google Chat alerts for outages and recovery
Add a Google Chat space webhook and PingInsight posts every confirmed outage and recovery as a card message — the monitor, error, and exact downtime laid out cleanly for teams on Google Workspace. Incoming webhooks post into the space they were created in, and PingInsight groups related messages by thread key so an outage and its recovery stay together rather than scattering across the space.
Set up in minutes
In-app path: Alerting → Channels → Add channel → Google Chat
- 1.Create an incoming webhook for the Google Chat space you want alerts in.
- 2.Add a Google Chat channel under Alerting and paste the webhook URL.
- 3.Attach it to monitors, an escalation policy, or an on-call schedule.
- 4.Send a test alert to confirm it posts to the space.
What you can do
- ✓Card-formatted down/up alerts in your Google Chat space
- ✓Recovery posted in the same thread as the original outage
- ✓SSL and domain-expiry reminders for Workspace teams
- ✓Keep alerting inside Google Workspace where your team works
A sample Google Chat alert
!PingInsight→ Google Chatnow
▌ Card — Google Chat space 🔴 api.example.com is DOWN HTTP 503 · confirmed by 2 of 3 regions · 14:03:07 UTC ────────── 🟢 Recovered — back up after 6m 21s (same thread)
Exact formatting varies by Google Chat; the live alert includes the monitor, confirming regions, and the precise downtime on recovery.
Frequently asked questions
- Why can't I create an incoming webhook in my space?
- Incoming webhooks must be enabled for the space, and your Workspace admin may restrict who can add them. Webhooks also can't be added to one-to-one direct messages — use a named space, create the webhook there, and paste its URL under Alerting.
- Why aren't recovery messages threading with the outage?
- Google Chat threads messages by thread key, and only spaces set to threaded replies will visibly group them. Confirm the space uses threaded conversations; in flat spaces each alert appears as its own message even though it carries the same key.
- The webhook URL expired or rotated — what do I do?
- Regenerate the incoming webhook in the Google Chat space, then paste the new URL into the Google Chat channel under Alerting and send a test alert. Old URLs stop delivering once rotated, which is the usual reason alerts silently stop.
See all alerting integrations or read about incident management.
Start monitoring in under a minute
Free forever, no credit card. Upgrade when you need finer intervals.