> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/chatops/google-chat/incoming-webhook.md). # Post alerts with a Google Chat webhook Post ilert alerts to a Google Chat space through an incoming webhook, where the ilert app cannot be installed. {% hint style="warning" %} Prefer the [ilert Google Chat app](/chatops/google-chat/google-chat-app.md). A webhook only posts messages: nobody can accept, reroute, or resolve from the space, the card is never updated as the alert changes, and the slash commands do not exist. Use this route only where the app cannot be installed for your organization. {% endhint %} ## In Google Chat: create the webhook {% stepper %} {% step %} ## Open the space's apps and integrations In the space where you want alerts, open the space menu and choose **Apps & integrations**.

A Google Chat space menu open, with Apps and integrations highlighted among options such as Manage members, Space settings, and Space details. — Open the space menu, not the space settings.

{% endstep %} {% step %} ## Add a webhook Select **Webhooks**, then click **Add webhooks**.

The Apps and integrations panel for a Google Chat space, showing an Apps section and an empty Webhooks section with an Add webhooks button. — Webhooks sit under Apps and integrations, below the apps.

{% endstep %} {% step %} ## Name it Enter a name and, optionally, an avatar URL — use `https://cdn.ilert.com/favicon.ico` for the ilert icon. Click **Save**.

The avatar URL is optional; this one gives the webhook the ilert icon.

{% endstep %} {% step %} ## Copy the webhook URL Open the new webhook's menu and choose **Copy link**.

The Webhooks list showing one ilert webhook whose URL is shown here with SPACE_ID, KEY and TOKEN placeholders, with its overflow menu open on Copy link, Edit, and Delete. — Treat this URL as a secret — anyone holding it can post to the space.

{% endstep %} {% endstepper %} ## In ilert: create the alert action {% stepper %} {% step %} ## Start a new alert action In the sidebar, go to **Alerting** → **Alert actions** and click **Create new alert action**. {% endstep %} {% step %} ## Choose Google Chat, with the webhook option Select the **Google Chat** tile and tick **Use webhook**. Click **Next**. {% endstep %} {% step %} ## Choose the alert sources and the events to publish Pick the alert sources whose alerts should reach the space, and tick the events to publish. Only **Alert created** is ticked to begin with, and every event you add becomes its own message. **Trigger mode** stays on **Automatic**. Click **Next**. {% endstep %} {% step %} ## Skip the conditions Set conditions under **Conditional execution**, or click **Next** to publish every alert of those sources. {% endstep %} {% step %} ## Paste the webhook URL Name the alert action, paste the link you copied into **URL**, and click **Save**. Click **Save** again on the edit page to reach the detail page. {% endstep %} {% step %} ## Test it Click **Test** in the top right. A test message appears in the space. {% endstep %} {% endstepper %} ## What arrives in the space The webhook receives the same card as the ilert app posts — status, summary, details, escalation policy, priority, labels, responders, links, affected services, and images — **without the buttons**, and always in English. Every event you tick posts a new message. Nothing is updated in place, so a busy alert produces a series of messages. ## Keep an alert's messages together Add `&messageReplyOption=REPLY_MESSAGE_FALLBACK_TO_NEW_THREAD` to the webhook URL, exactly as written, and ilert groups the messages **per alert**: the first message about an alert starts a thread, and every later message about that alert is a reply in it. Different alerts still get different threads. Given a webhook link of: ``` https://chat.googleapis.com/v1/spaces/AAPQRs0mVWx/messages?key=KKKKKK&token=TTTTTT ``` use: ``` https://chat.googleapis.com/v1/spaces/AAPQRs0mVWx/messages?key=KKKKKK&token=TTTTTT&messageReplyOption=REPLY_MESSAGE_FALLBACK_TO_NEW_THREAD ``` Without that parameter, every message stands on its own. ## FAQ ### Can I use several webhooks? Yes. Create one alert action per webhook URL, each with its own space and its own trigger events. ### The messages stopped arriving Open the alert action and read **Alert action logs** on its detail page. A webhook whose space was deleted, or that was removed in Google Chat, shows up there. Create a new webhook and paste the new URL into the alert action. ### Can responders act on these messages? No. Install the [ilert Google Chat app](/chatops/google-chat/google-chat-app.md) for that. --- # 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.ilert.com/chatops/google-chat/incoming-webhook.md?ask=&goal= ``` `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.