> ## Documentation Index
> Fetch the complete documentation index at: https://docs.openlayer.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Google Chat notifications

> Post workspace and project events to a Google Chat space by adding it as a notification destination with an incoming webhook.

Google Chat notifications are configured **team-wide** under **Workspace
settings** → **Notifications**. Each Google Chat space you add is a
**destination**: the space, the events it receives, and the projects those
events come from. Openlayer posts to the space through an incoming webhook that
you create in Google Chat, so there's nothing to authorize, and you don't need
Slack connected.

## Prerequisites

* The **Admin** role in Openlayer to add, edit, pause, or delete destinations.
  Other roles can view them.
* A Google Chat space you can add webhooks to. Your Google Workspace admin can
  turn incoming webhooks off for your organization. If the space doesn't let
  you add one, ask them to allow incoming webhooks.
* On a self-hosted Openlayer deployment, the platform must be able to reach
  `chat.googleapis.com` over HTTPS (port 443).

## Create a webhook in the space

**1. Open the space's webhooks**

In Google Chat on the web, open the space and choose **Apps &
integrations** → **Webhooks**.

**2. Add a webhook**

Give it a name your team recognizes, such as `Openlayer`. Google Chat shows
that name as the sender of Openlayer's messages.

**3. Copy the webhook URL**

The URL looks like
`https://chat.googleapis.com/v1/spaces/<space>/messages?key=…&token=…`.
Copy all of it, including the `key` and `token`.

> [!WARNING]
>
> The webhook URL lets anyone who has it post to the space. Treat it like a
> password. Openlayer never shows it again after you save the destination.

## Add the destination

On **Workspace settings** → **Notifications**, click **Add destination** and
choose **Google Chat**. Enter a **Space name** and paste the **Webhook URL**.
Google Chat doesn't share a space's name with webhooks, so the name you enter is
how the destination is listed in Openlayer. Then choose the events the space
receives and the projects they come from, as for any
[destination](https://docs.openlayer.com/notifications/slack.md#destinations).

After you save, open the destination's **⋯** menu and choose **Send test
message**. A test card from Openlayer appears in the space.

A space can be a destination only once per workspace. To send different events to
different spaces, create a webhook in each space and add each one as its own
destination.

## What the messages look like

* Each notification is a card with a button that opens the related page in
  Openlayer, such as the commit or test.
* When a failing test recovers, the recovery posts as a new message. Google Chat
  destinations don't reply in the failure's thread the way Slack does.
* If the destination receives the **Weekly digest**, the digest posts to the
  space too.

## Change the webhook

When you edit a Google Chat destination, the **Webhook URL** field is empty. The
current webhook is kept unless you paste a new one, so you can change events,
projects, or the space name without the URL.

A new URL must come from the same space. To move notifications to another space,
add a new destination for that space and delete the old one.

## When messages stop arriving

If Google Chat rejects the webhook, for example because the webhook or the space
was deleted or incoming webhooks were turned off for your Google Workspace,
Openlayer stops posting to the destination. Its row shows **Not delivering**.
Hover over it to see what went wrong and how to fix it. Notifications for that
destination are skipped while it isn't delivering. They aren't queued for
later.

To fix it, add a new webhook in the same space, edit the destination, paste the
new URL, and save. Delivery resumes right away. If the original webhook works
again, for example because your Google Workspace admin turned webhooks back on,
a successful **Send test message** also resumes delivery.

Temporary errors from Google Chat, such as rate limits or outages, are retried
automatically and don't stop the destination.

## Troubleshooting

| Symptom | Likely cause | Fix |
| - | - | - |
| "That is not a Google Chat webhook URL" | The URL isn't an incoming webhook URL, or it was cut off when copied | Copy the full URL from **Apps & integrations** → **Webhooks**, including its `key` and `token` |
| "This webhook posts to another Google Chat space" | You pasted a webhook from a different space while editing | Add a new destination for that space instead |
| **Not delivering**: "Google Chat rejected the webhook" | The webhook or space was deleted, or incoming webhooks were turned off | Add a new webhook in the space, then edit the destination and paste its URL |
| **Not delivering**: "Openlayer cannot read this destination's webhook URL" | The workspace moved to another Openlayer deployment | Copy the URL from the space again, then edit the destination and paste it |
| **Google Chat** isn't offered when you add a destination | Google Chat is turned off for your Openlayer deployment | Ask your Openlayer administrator to enable it |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.