Oopsbell: documentation

• A Sentry organization (sentry.io, US or EU region; self-hosted via Internal Integration). Installing needs permission to manage integrations (Owner or Manager role).
• Google Workspace with Google Chat. Your admin must allow incoming webhooks (Admin console → Apps → Google Workspace → Google Chat → Chat apps → “Allow users to add and use incoming webhooks”).

1. Install the integration from Sentry (Settings → Integrations → Oopsbell) and accept the permissions. You land in the dashboard.
   Self-hosted Sentry or before the listing is public: open https://oopsbell.sperar.com/connect and follow the Internal Integration steps (about 5 minutes).
2. Add a Space: in Google Chat (web), open the Space → name ▾ → Apps & integrations → Webhooks → add one called “Sentry”, copy the URL, paste it into the dashboard. A test message confirms it works.
3. Route alerts: in Sentry, create or edit an alert and add the action “Send to Google Chat”. Pick the Space; optionally mention everyone and add a runbook note. Each alert decides which projects and environments go to which Space.

• A card per alert: issue title, project · environment · level, where it happened, top in-app frames, release, alert rule, and buttons Open in Sentry, Resolve, Archive.
• One thread per issue. Repeat alerts and status changes (resolved, archived, regressed, assigned) are replies in that thread when the integration has the issue webhook.
• Resolve / Archive open a confirmation page; the change is made in Sentry by the integration and noted as a comment “Resolved from Google Chat (Space: …)”. Each button works once and expires after 7 days. Archive means “archived until escalating”.
• Metric alerts: critical, warning and resolved of one incident share a thread.

• Google Chat accepts one message per second per Space. We queue messages per Space; during an alert storm (more than 30 queued) queued cards are collapsed into one summary message.
• Google Chat doesn't let webhook messages be edited, so the original card is a snapshot; updates arrive as thread replies.
• Spaces that don't use threads get replies as separate messages.

• No “Webhooks” item in the Space menu: your Workspace admin has disabled incoming webhooks, or you are in the mobile app (webhooks are added on the web).
• Space shows “rejected by Google”: the webhook was deleted or blocked. Remove the Space in the dashboard and add a new webhook.
• Resolve says the connection lost access: the integration was uninstalled or its token revoked. Reinstall it.
• Sign in again: on the sign-in page enter your organization slug; a one-time link is posted to your connected Spaces.

Uninstall in Sentry (Settings → Integrations). We then delete your connected Spaces, tokens and thread references immediately. For an Internal Integration, delete it in Sentry and remove the Spaces in the dashboard, or ask support to delete the account.

Alert payloads are processed in memory and are not stored. Personal data in titles (emails, IP addresses, tokens) is masked before it reaches Chat. See the privacy policy.

Email support@sperar.com.

• 2026-10-24: First beta: issue and metric alerts, threads per issue, Resolve / Archive from Chat, Internal Integration and public install.