Google Chat integration

The Google Chat integration posts alerts into a space as cardsV2 messages, through the space’s incoming webhook URL.

What you need

In Google Chat, open the space you want alerts in.
Apps & integrations → Webhooks → Add webhook.
Copy the URL. It looks like https://chat.googleapis.com/v1/spaces/....

Connect it

In the dashboard, go to Manage → Integrations and click the Google Chat card. Name it, paste the URL into Webhook URL, and click Add integration.

Or through the API, with POST /integration/google_chat:

curl -X POST https://api.siteqwality.com/integration/google_chat \
  -H "Authorization: Bearer $SITEQWALITY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "friendly_name": "Acme Google Chat",
    "url": "https://chat.googleapis.com/v1/spaces/..."
  }'

The URL must start with https://chat.googleapis.com/v1/spaces/. Whether the webhook still works is not checked, so a deleted webhook shows up as a failed notification. The URL carries its own auth token and never reads back in full, so keep your own copy; to change it, choose Edit in the integration’s ⋯ menu and paste the new one.

Add it to a notification group

Right after you add the integration, the dashboard offers to do this for you: choose a group or create one, choose which monitors alert that group (the ones that already do, every monitor, or ones you pick), then send a test. If you skipped it, Route alerts on the integration’s card opens the same step. To do it by hand:

Go to Respond → Notifications. Click a group’s name to open it, or click Add group to make a new one.
Under Notifications, click Add notification method. Set Notification type to Google Chat and choose this integration under Integration.
Click Done editing, then Save changes (Create group for a new group).

Through the API, create the channel with POST /notification:

curl -X POST https://api.siteqwality.com/notification \
  -H "Authorization: Bearer $SITEQWALITY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "notification_group_id": "<your-group-id>",
    "type": "google_chat",
    "details": { "google_chat_integration_id": "<google-chat-integration-id>" }
  }'

Message format

Messages render as a Google Chat card with a header and a body section carrying the monitor name, URL, and status. Recovery messages use the same card shape.

Delivery behavior

A failed send can get up to 3 attempts in quick succession but is never retried later, and the outcome is always recorded. If Google Chat is your only alerting path for something that matters, pair it with a second channel. See delivery guarantees.

Limitations

Heartbeat (cron) monitors, TLS certificate alerts, page speed alerts and DNS record changes do not reach Google Chat. See the coverage table.