# Google Chat (/en/docs/platform/features/alerting/channels/google-chat)



A Google Chat channel type posts each alert as a message in one Chat space, through the space's [incoming webhook](https://developers.google.com/workspace/chat/quickstart/webhooks). Create the webhook in the space, paste its URL into CentralCSP, send a test.

## Prerequisites [#prerequisites]

* The website **Manager** role in CentralCSP.
* A Google Workspace account. Webhooks are a Workspace feature; personal Google accounts cannot create them, and your organization must allow them.
* A Chat space you can manage.

<Callout type="info">
  Webhooks are managed from Google Chat in a desktop browser. The mobile app cannot create or edit them.
</Callout>

## 1. Create the webhook in Google Chat [#1-create-the-webhook-in-google-chat]

1. Open [Google Chat](https://chat.google.com) in a browser and enter the space that should receive alerts.
2. Select the space name to open its menu, then **Apps & integrations**.
3. Select **Add webhooks** (under **Webhooks**).
4. Name it (for example `CentralCSP alerts`), optionally set an avatar URL, and select **Save**.
5. Open the webhook's **More** menu and select **Copy link**. The URL starts with `https://chat.googleapis.com/v1/spaces/`.

Google's own guide is at [Build a Google Chat app as a webhook](https://developers.google.com/workspace/chat/quickstart/webhooks).

A webhook only posts to the space it was created in. Treat the URL as a secret; anyone holding it can post to the space.

## 2. Add the channel in CentralCSP [#2-add-the-channel-in-centralcsp]

1. In the dashboard, go to **Alerts** > **Configuration** > **Add channel**.
2. Name the channel, choose the **Google Chat** type, and paste the webhook URL.
3. Save.

The URL is validated as you type: it must be on `chat.googleapis.com` with a path starting `/v1/spaces/`, so a space link or a chat page URL pasted by mistake is rejected before you save.

## 3. Test the channel [#3-test-the-channel]

Select **Test** on the new channel. A sample alert built from a fake CSP violation is sent immediately.

If the message does not arrive, the webhook was refused. Check that the webhook still exists under **Apps & integrations** and that your organization still allows webhooks in that space; a deleted webhook fails permanently.

## Next steps [#next-steps]

* [Create a rule](/en/docs/platform/features/alerting/rules) that delivers to this channel.
* [Channels overview](/en/docs/platform/features/alerting/channels) for auto-disable behaviour and limits.
* [Delivery history](/en/docs/platform/features/alerting/deliveries) to audit what was sent.