Get monitoring alerts in a Google Chat space your team already follows, with a link straight to the failing monitor.
What the alerts look like#
A plain-text card lands in the space: monitor name, status, reason, and a clickable link to the incident page. Google Chat doesn't support rich embeds the way Discord or Teams do, but the message is structured enough to read in one glance from a phone notification.
Before you start#
Two requirements:
- A Google Workspace account. Webhooks aren't available on personal Gmail accounts, only on paid Workspace plans.
- A WatchCron account on any plan. Google Chat alerts are included on Free, Starter, Pro and Business.
Step 1 — Add a webhook to the space#
Open the space where you want alerts. Click the space name at the top, then Apps & integrations.
Click Add webhooks, name it "WatchCron", and save. The webhook appears in the list with a three-dot menu (⋮) next to it. Click ⋮ → Copy link.
| Where | What to do |
|---|---|
| Space name → Apps & integrations | Click Add webhooks, name it "WatchCron" |
| Webhook row → ⋮ | Click Copy link |
The URL is long and contains a key= and token= parameter. That's expected.
Step 2 — Add the channel in WatchCron#
Go to Alerts → Channels → Add channel and choose Google Chat.
| Field | What to enter |
|---|---|
| Label | A name you'll recognise, e.g. "Ops space" |
| Webhook URL | The URL you copied. Starts with https://chat.googleapis.com/v1/spaces/ |
Click Save.
Step 3 — Test and assign monitors#
Hit Send test. A message should appear in the space within seconds. If it does, you're done with the plumbing.
Open any monitor and tick the Google Chat channel under Alert channels. Assign as many monitors as you like: one webhook handles all of them.
What to paste where#
| WatchCron field | Value | Where you find it |
|---|---|---|
| Webhook URL | https://chat.googleapis.com/v1/spaces/AAAA…/messages?key=…&token=… | Space → Apps & integrations → ⋮ → Copy link |
What WatchCron sends#
Each message contains the monitor name, current status (down or recovered), a short reason, and a link to the incident. Recovery messages follow the same format, so scrolling up through the space gives you a quick timeline of what broke and when it came back.
Google Chat doesn't thread webhook messages the way Zulip does. If you want failures and recoveries grouped together, pin the space and check it after each recovery.