Google Chat alerts from AlertHub incoming webhooks

Google Workspace shops live in Chat (and Gmail), not Slack. The default path is a Chat incoming webhook per SaaS, then a graveyard of unused space URLs when someone renames the room.

AlertHub treats Google Chat like Discord or Teams: you paste one incoming webhook on the project. Sources stay on https://api.thealerthub.com/sendAlert (or email ingest). AlertHub detects Chat (gchat) and posts a card with project, level, title, and description.

Docs: Google Chat destination.

How Chat delivery works

In Google Chat, open the space → Apps & integrations (or space settings) → Webhooks → create an incoming webhook. Copy the URL.
In AlertHub: project Connections → Webhooks → paste the URL.
Warning and critical alerts become Chat cards. Info stays in the dashboard.

Google’s webhook UI moves occasionally; the URL still looks like chat.googleapis.com. If AlertHub does not format a card, confirm you saved a Chat webhook (not a generic HTTPS endpoint).

Setup (once)

Create a project at app.thealerthub.com.
Create the Chat incoming webhook on the ops space (not a customer-facing space).
Paste it in AlertHub and send a test warning via the Ingestion API.

Alert 1: Workspace-native on-call

Many companies already mute Slack. Put Stripe failures, uptime, and GitHub Actions on the same AlertHub project so Chat is the only extra destination to add.

Alert 2: Chat + Gmail destination

AlertHub also has an email destination for people who refuse Chat notifications. Same sources; Chat for the space, email for the auditor who lives in Gmail.

Alert 3: Migrate off per-app Chat webhooks

When each vendor has its own Chat webhook, rotating the space means touching Stripe, Shopify, and CI. Move ingest to AlertHub (Shopify, email ingest), then keep a single Chat URL in Connections.

Ideas to squeeze more value

Spaces vs DMs. Incoming webhooks post to a space. For a personal ping, prefer Telegram, WhatsApp Pro, or mobile push.
Do not mix customers into the ops space. PII in order emails is easier to overshare in Chat than in a private Telegram.
Same pattern as Teams. If a subsidiary uses Teams, add Microsoft Teams on another project.

FAQ

Is Google Chat a first-class destination?
Yes. AlertHub formats Chat cards when the stored webhook is classified as Google Chat, same family as Discord and Teams.

Can I use Hangouts Chat legacy URLs?
Use a current incoming webhook from Google Chat. Recreate it if an old URL returns 404.

Do info alerts appear in the space?
No. Raise the source level when the space should see it.

Next steps

Paste a Chat webhook in Connections, follow the Google Chat setup, and send one test warning. Add Slack only if a second team still lives there.