> For the complete documentation index, see [llms.txt](https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/get-started/messaging/google-chat.md).

# Google Chat

Connect Google Chat to Heeler with incoming webhooks — a two-minute setup, no OAuth or service accounts.

Heeler delivers workflow notifications to Google Chat Spaces using **incoming webhooks** — a self-service setup that takes about two minutes. **No OAuth, service accounts, or Marketplace app** are required.

{% hint style="info" %}
Google Chat webhooks require a **Google Workspace** account (Business or Enterprise). Personal Google accounts don't support incoming webhooks.
{% endhint %}

## Step 1 — Create the integration

Go to **Administration → Integrations → Add Integration → Google Chat**, enter an **Integration Name** (e.g. `Google Chat Notifications`), and **Save**. No credentials are needed yet.

## Step 2 — Generate a webhook in Google Chat

For each Space you want notifications in:

1. Open the Space, click its **name** at the top, and select **Apps & integrations**.
2. Click **Add webhooks**, enter a name (e.g. `Heeler Security`) and optional avatar, and **Save**.
3. Copy the generated **webhook URL** (form `https://chat.googleapis.com/v1/spaces/.../messages?key=...&token=...`).

{% hint style="info" %}
Unlike Teams Workflows webhooks, Google Chat webhooks **don't expire** — but a Space admin can delete them, so the test button is handy for ongoing verification.
{% endhint %}

## Step 3 — Add webhooks in Heeler

On the Google Chat integration row, open the **⋯** menu → **Manage Webhooks** → **Add Webhook**, enter a **Label** and paste the **Webhook URL**, and **Add Webhook**. Repeat for each Space. Use a webhook's **⋯ → Send Test Message** to verify.

## Step 4 — Use it

In a workflow's **Action** step, choose **Send Google Chat Message**, then pick the **Connection** and **Webhook Destination**. You can also set a default Space on a repository, service, or module via its **Channel** field.

## Troubleshooting

<table><thead><tr><th width="330">Issue</th><th>Fix</th></tr></thead><tbody><tr><td>"Send Google Chat Message" missing in actions</td><td>Ensure a Google Chat integration exists under Administration → Integrations.</td></tr><tr><td>Webhook test fails with an HTTP error</td><td>Verify the URL and that incoming webhooks are enabled for your Workspace org.</td></tr><tr><td>No webhook destinations in the workflow dropdown</td><td>Add webhooks via <strong>Manage Webhooks</strong> on the integration row.</td></tr><tr><td>"Add webhooks" not available in a Space</td><td>Your Workspace admin must enable incoming webhooks for the organization.</td></tr><tr><td>Webhook deleted by a Space admin</td><td>Generate a new URL in Google Chat and add it in Heeler.</td></tr></tbody></table>

## Related

* [Connect Messaging](/mrecEO40m5D6bt7Pq5pE/get-started/messaging.md) — the other supported messaging tools.
* [Actions](/mrecEO40m5D6bt7Pq5pE/operate/workflows/actions.md) — the workflow action that sends the message.
* [Routing and Templates](/mrecEO40m5D6bt7Pq5pE/operate/workflows/routing-and-templates.md) — controlling message content and destination.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/get-started/messaging/google-chat.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.