INTEGRATION

Google Chat

Post a card to a Google Chat space via a space webhook.

How the wire-up works

Three things to know: the protocol, the credential, and what the alert payload looks like. The setup is the same on free and Pro.

Protocol
discord-webhook
Credential
A Google Chat space webhook URL (created under the space's Apps & integrations → Webhooks).
Payload
CardV2 JSON with a header (down/up) and a section listing the monitor name, latency, status, and a link. Same card format regardless of whether the alert is DOWN or RECOVERY.

What it supports

The grid below describes what the channel itself supports once wired up. All channels are available on the free plan unless the badge says otherwise.

Free planSupportedNo card, no expiry.
Pro planSupportedSame on free and Pro.
InteractiveNot supportedOne-way push only.
Incoming mentionsNot supportedOutbound-only.
Rich attachmentsSupportedCards, embeds, colour-coded status.
TLS in transitSupportedHTTPS / WSS — no plaintext fallback.

When Google Chat is the right pick

Your team uses Google Workspace and the alerts need to land in the same space as the rest of the incident chat.

Wire Google Chat to ZnowPulse in two minutes.

Free plan. No card. Cancel any time.