Google Chat
Send analysis results to a Google Chat space using an incoming webhook
Connect a Google Chat space using an incoming webhook URL. SigSentry posts formatted card messages.
This page is for outbound delivery. For inbound slash commands in Google Chat, see Google Chat triggers.
Prerequisites
| Need | Notes |
|---|---|
| Google Workspace account | Google Chat enabled for your domain |
| A target Chat space | Where you want SigSentry to post |
| Permission to add apps to the space | Usually any space member |
Setup walkthrough
Open the space and add the webhook
In Google Chat, open the space. Click the space name at the top, then Apps & integrations → Add webhooks.
Configure the webhook
| Field | Value |
|---|---|
| Name | SigSentry |
| Avatar URL | (Optional) e.g. https://docs.sigsentry.com/logo.png |
Click Save. Google Chat generates a webhook URL — copy it.
Add the channel in SigSentry
In the dashboard, Project → Channels → Add Channel.
| Field | Value |
|---|---|
| Type | Google Chat |
| Name | Descriptive label, e.g. #engineering-alerts-gchat |
| Webhook URL | The Google Chat webhook URL |
| Severity threshold | Lowest severity that should trigger this channel |
Save and test
Click Save. Run a test analysis to verify the card posts to the Chat space.
What gets posted
Each Google Chat message includes:
- A severity badge and the analysis summary
- The root cause and affected services
- A button linking back to the full analysis in the dashboard
Webhook security
Google Chat webhook URLs are unauthenticated. Treat them like secrets. To revoke, delete the webhook in the space's Apps & integrations panel.
Troubleshooting
| Error | Fix |
|---|---|
400 invalid argument | Card payload rejected — usually a card schema issue. Retry; if persistent, contact support |
| Webhook URL doesn't work | Webhook may have been removed; recreate in the space |
| Workspace has webhooks disabled | Your admin has restricted webhooks — ask for an exception or use the generic webhook channel |