Google Chat via the Webhook channel
Google Chat is not one of our native channels, and we will be straight with you about that. You connect it through the native Webhook channel by pointing a PulseStack webhook at a Google Chat space incoming webhook. Setup takes minutes and every alert lands where your team already talks.
14-day trial. No card needed on Free. Failure and recovery alerts on every channel.
There is no dedicated Google Chat button in PulseStack, and inventing one would only mislead you. Instead you use the Webhook channel, one of our eight native channels, and point it at a Google Chat space incoming webhook. Google Chat receives the payload and renders it as a message card. That is the whole trick, and it is reliable.
In your target space, open Apps and integrations, then Manage webhooks, and add an incoming webhook. Google gives you a unique URL for that space.
Go to Alert channels, choose Webhook, and paste the Google Chat URL. This is the native channel that carries the Google Chat delivery.
Select which of your monitors should notify this channel. Mix HTTP, keyword, TCP ping, port, API, heartbeat, DNS and domain expiry checks freely.
Choose a consecutive-failure threshold to cut noise, keep recovery alerts on, and send a test. The next state change posts straight into the space.
Every message carries enough context to triage without leaving the space. No hunting through dashboards to work out what changed.
PulseStack posts a compact JSON body to your Google Chat webhook URL. Google Chat reads the text field and renders it in the space. Here is a representative shape.
{
"text": "Monitor DOWN: api.acme.io",
"monitor": "api.acme.io",
"state": "down",
"previous_state": "up",
"http_status": 503,
"reason": "timed out after 30s",
"location": "London, UK",
"consecutive_failures": 3,
"response_time_ms": null,
"timestamp": "2026-07-25T10:42:07Z",
"incident_url": "https://app.pulsestack.io/i/48213"
}The same channel later posts a recovery message with state set to up when the check passes again.
Google Chat rides on Webhooks, highlighted below. Everything else in this row is a first-class native channel you can enable directly. Zapier and Google Chat are not native and both connect through Webhooks.
SMS and voice are a Team and Enterprise add-on.
Route any combination of these into the same space. Whatever breaks, the room hears about it.
Watch a URL for status, content and response time.
Alert when expected text appears or vanishes from a page.
Confirm a host answers at the network level.
Check a specific service port is open and responding.
Validate a JSON endpoint with custom request and checks.
Catch cron jobs and workers that fail to check in.
Detect record changes and resolution failures.
Get warned well before a domain lapses.
If your team already lives in Google Chat, route incidents there so nobody has to watch a separate tool. The Webhook channel drops PulseStack alerts straight into the space you already read.
Give each product or client its own space and its own Webhook channel. Failures land exactly where the responsible people are looking, with no cross-posting.
Set a consecutive-failure threshold so a single flaky check does not spam the room. When the endpoint truly goes down, the message posts once, then again on recovery.
Send low-urgency notices to Google Chat via webhook while critical monitors also hit the native PagerDuty channel. One monitor can notify several channels at once.
10 monitors, 60s checks, all types
50 monitors, SSL, DNS and domain insights
100 monitors, server diagnostics, 3 seats
200 monitors, 30s checks, 5 seats
Free covers 5 HTTP monitors on a 5 minute interval with no card. Custom webhook routing needs a paid plan.
No. Google Chat is not a dedicated native app. It connects through PulseStack's built-in Webhook alert channel, which you point at your Google Chat space's incoming webhook URL. PulseStack ships eight native alert channels in total: Email, SMS, Slack, Microsoft Teams, Discord, PagerDuty, Telegram and Webhooks.
Create an incoming webhook inside your Google Chat space under Apps & integrations, copy the webhook URL, then add a new alert in PulseStack using the Webhook channel and paste that URL as the endpoint. Attach the alert to your monitors and save.
Alerts fire on both failure and recovery, after a configurable consecutive-failure threshold. That threshold lets you skip single-check blips so the space only reflects real incidents.
Any of them. The Webhook channel works with all six core monitor types - HTTP, Keyword, TCP Ping, Port, API and Heartbeat - as well as the DNS and Domain Expiry monitors.
Webhook alerts are available on every paid plan, starting with Starter at £15 per month, and each paid plan comes with a 14-day trial. The Free plan is limited to HTTP monitors.
Yes. Create a separate incoming webhook for each space and add a matching Webhook alert in PulseStack, so different rooms and teams can receive the monitors that are relevant to them.
Point a PulseStack Webhook channel at your Google Chat space and start receiving clean, actionable incident and recovery messages in minutes. Honest setup, no invented native badge, just reliable delivery.