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 and Free plan, both with no card needed. Failure and recovery alerts on every channel.
Monitor DOWN: api.acme.io
https://api.acme.io/health (HTTP)
Error: Down from 2/3 locations: London, New York
London: down, 503, 412 ms
New York: down, 503, 388 ms
Sydney: up, 200, 291 ms
Time: 2026-07-25T09:42:07.000Z
Example. A Monitor RECOVERED message follows when it is back up. Google Chat shows the name and avatar you give the webhook.
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. PulseStack recognises the Google Chat address and posts a plain text message the space can show. That is the whole trick.
In your target space, open Apps and integrations, then Manage webhooks, and add an incoming webhook. Google gives you a URL for that space that starts https://chat.googleapis.com/.
Open Alert Contacts, click Add contact, choose Webhook and paste the Google Chat URL into Webhook URL. PulseStack™ recognises the address and sends plain text.
Tick the contact under Notify on failure on each monitor that should post to the space. Mix HTTP, keyword, TCP ping, port, API, heartbeat, SSL certificate, DNS record and domain expiry checks freely.
Click Send test. The space should show “This is a test notification from PulseStack.” From then on, every failure and recovery 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.
Google Chat only accepts its own message format, so when the webhook address is a Google Chat one, PulseStack posts a plain text message instead of its usual JSON payload. Here is an example request body; Google Chat shows the words between asterisks in bold.
{
"text": "🔴 *Monitor DOWN*: api.acme.io\nhttps://api.acme.io/health (HTTP)\nError: Down from 2/3 locations: London, New York\nLondon: down, 503, 412 ms\nNew York: down, 503, 388 ms\nSydney: up, 200, 291 ms\nTime: 2026-07-25T09:42:07.000Z"
}When the check passes again, the same space gets a Monitor RECOVERED message saying how long it was down. Any other webhook address receives the full JSON payload described on the webhooks page.
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 alerts are included on Team and Enterprise. See all integrations.
Route any combination of these nine 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 accepts a TCP connection, and how fast.
Check a specific service port is open and responding.
Send your own method, headers and body, and check the status code.
Catch cron jobs and workers that fail to check in.
Get warned a set number of days before expiry (7 by default), or when the certificate is not trusted.
Alert when a record goes missing or stops matching what you expect.
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.
Every failure is double-checked first, 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.
50 monitors, 60s checks, all types, SSL and DNS insights
150 monitors, 30s checks, competitor tracking
500 monitors, server diagnostics, 3 seats
2,000 monitors, 5 seats, PDF reports
Free covers 5 HTTP monitors on a 5 minute interval with no card. Custom webhook routing needs a paid plan.
Start with Send test next to the contact on the Alert Contacts page. The space should show “This is a test notification from PulseStack.” straight away; if Google refuses it, the error reads Webhook returned, followed by the status code.
PulseStack™ only switches to Google Chat's plain text format for URLs that start exactly like that. Any other address gets the full JSON payload, which Google Chat rejects (HTTP 400) because it does not know fields such as event. Copy the webhook URL from the space again, in full.
A Google Chat webhook URL ends with key and token parameters. If either is missing, or someone deleted the webhook from the space, Google refuses the post. Add a new webhook and replace the contact.
Incoming webhooks need a Google Workspace account, and a Workspace administrator can switch them off. If you cannot add a webhook in the space, ask your administrator.
Google Chat limits how fast a space accepts webhook messages. If lots of monitors change state together, some posts can be refused, and PulseStack™ posts each alert once without retrying.
Alerts go to the contacts ticked under Notify on failure (every contact if none are ticked), and only when a monitor goes down or recovers. If an alert looks wrong, see why a monitor status can be wrong.
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.
In your Google Chat space, open Apps & integrations, add a webhook and copy its URL (it starts https://chat.googleapis.com/). In PulseStack™, open Alert Contacts, click Add contact, choose Webhook, paste the URL and click Send test. Then tick the contact under Notify on failure on your monitors.
Alerts fire on both failure and recovery. A failed check is re-tested a few seconds later, and a monitor is only marked down when at least two of the three check locations fail, so single-check blips are skipped and the space only reflects real incidents.
Any of them. The Webhook channel works with all nine monitor types: HTTP, Keyword, TCP Ping, Port, API, Heartbeat, SSL certificate, DNS record and domain expiry.
Webhook alerts are available on every paid plan, starting with Starter at GBP 9 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.