Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.scrubbe.com/llms.txt

Use this file to discover all available pages before exploring further.

Scrubbe integrates with the tools your team already uses so that incidents are detected, routed, and communicated without manual effort. Notification integrations deliver real-time alerts to your team, source code integrations surface deployment context on every incident ticket, and monitoring integrations funnel events from your infrastructure into the Scrubbe incident pipeline automatically. All OAuth-based integrations follow the same pattern: your Scrubbe user initiates the connection with a POST to /api/v1/integrations/{provider}/connect, Scrubbe returns an OAuth authorization URL, you visit that URL to grant access, and Scrubbe completes the handshake via the provider’s callback endpoint. You need the ENGINEER role or higher to connect any integration.

Notification integrations

Send incident alerts to your team wherever they work.

Slack

Receive real-time incident alerts in any Slack channel. Configure which events trigger notifications through your IMS settings.

Twilio SMS

Send SMS alerts to on-call engineers via Twilio. Connect by posting your Twilio credentials to POST /api/v1/integrations/sms/connect.

Twilio WhatsApp

Deliver incident notifications over WhatsApp. Connect by posting your Twilio WhatsApp number to POST /api/v1/integrations/whatsapp/connect.

Source code and deployment integrations

Link deployment events and commit SHAs to incident tickets automatically.

GitHub

Connect your GitHub repositories and receive deployment status events. Commit SHAs from failing deployments are linked directly to incidents.

GitLab

Connect your GitLab projects and ingest pipeline events. Failed pipelines and deployment jobs flow into the Scrubbe incident pipeline.

Meeting integrations

Spin up a war room the moment an incident opens.

Google Meet

Launch a Google Meet call directly from an incident ticket. Keep your response team in sync during active incidents without leaving Scrubbe.

Event ingestion (monitoring sources)

Route alerts from your monitoring and CI infrastructure into the Scrubbe incident pipeline.

Prometheus

Point your Alertmanager webhook receiver at Scrubbe to turn firing alerts into incident signals automatically.

Datadog

Send Datadog monitor alerts and events to Scrubbe via a webhook integration on your Datadog notification channel.

PagerDuty

Forward PagerDuty V2 incident webhooks to Scrubbe to correlate on-call alerts with your incident tickets.

Kubernetes

Ingest pod crash, OOMKill, and restart-loop events from your Kubernetes clusters.

GitHub Actions

Receive workflow_run and deployment_status events from GitHub Actions pipelines.

GitLab Pipelines

Ingest GitLab pipeline webhook events for failed or blocked jobs.

Generic webhook

Use the Scrubbe canonical payload format to send events from any custom monitoring tool or internal system.
All ingestion endpoints use API key authentication — not session-based JWT tokens. When configuring a webhook in an external tool, pass your Scrubbe API key in the X-API-Key request header. See the Event ingestion page for full setup instructions.

Twilio SMS

To configure SMS notifications, send a POST request to /api/v1/integrations/sms/connect with a Bearer token and your Twilio credentials in the request body. Scrubbe stores the connection and uses it to dispatch SMS alerts to on-call engineers when incidents are created or updated.

Twilio WhatsApp

To configure WhatsApp notifications, send a POST request to /api/v1/integrations/whatsapp/connect with your Twilio WhatsApp number. Scrubbe routes incident alerts through your Twilio WhatsApp sender after the connection is saved.