> ## 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 Integrations: Connect Your Toolchain

> Connect Scrubbe to monitoring tools, source code hosts, messaging platforms, and video conferencing to automate detection, alerts, and context enrichment.

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.

<CardGroup cols={2}>
  <Card title="Slack" icon="slack" href="/integrations/slack">
    Receive real-time incident alerts in any Slack channel. Configure which events trigger notifications through your IMS settings.
  </Card>

  <Card title="Twilio SMS" icon="message-square" href="/integrations/overview#twilio-sms">
    Send SMS alerts to on-call engineers via Twilio. Connect by posting your Twilio credentials to `POST /api/v1/integrations/sms/connect`.
  </Card>

  <Card title="Twilio WhatsApp" icon="message-circle" href="/integrations/overview#twilio-whatsapp">
    Deliver incident notifications over WhatsApp. Connect by posting your Twilio WhatsApp number to `POST /api/v1/integrations/whatsapp/connect`.
  </Card>
</CardGroup>

## Source code and deployment integrations

Link deployment events and commit SHAs to incident tickets automatically.

<CardGroup cols={2}>
  <Card title="GitHub" icon="github" href="/integrations/github-gitlab">
    Connect your GitHub repositories and receive deployment status events. Commit SHAs from failing deployments are linked directly to incidents.
  </Card>

  <Card title="GitLab" icon="gitlab" href="/integrations/github-gitlab">
    Connect your GitLab projects and ingest pipeline events. Failed pipelines and deployment jobs flow into the Scrubbe incident pipeline.
  </Card>
</CardGroup>

## Meeting integrations

Spin up a war room the moment an incident opens.

<CardGroup cols={2}>
  <Card title="Google Meet" icon="video" href="/integrations/google-meet">
    Launch a Google Meet call directly from an incident ticket. Keep your response team in sync during active incidents without leaving Scrubbe.
  </Card>
</CardGroup>

## Event ingestion (monitoring sources)

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

<CardGroup cols={2}>
  <Card title="Prometheus" icon="activity" href="/integrations/ingestion">
    Point your Alertmanager webhook receiver at Scrubbe to turn firing alerts into incident signals automatically.
  </Card>

  <Card title="Datadog" icon="bar-chart-2" href="/integrations/ingestion">
    Send Datadog monitor alerts and events to Scrubbe via a webhook integration on your Datadog notification channel.
  </Card>

  <Card title="PagerDuty" icon="bell" href="/integrations/ingestion">
    Forward PagerDuty V2 incident webhooks to Scrubbe to correlate on-call alerts with your incident tickets.
  </Card>

  <Card title="Kubernetes" icon="box" href="/integrations/ingestion">
    Ingest pod crash, OOMKill, and restart-loop events from your Kubernetes clusters.
  </Card>

  <Card title="GitHub Actions" icon="github" href="/integrations/ingestion">
    Receive `workflow_run` and `deployment_status` events from GitHub Actions pipelines.
  </Card>

  <Card title="GitLab Pipelines" icon="gitlab" href="/integrations/ingestion">
    Ingest GitLab pipeline webhook events for failed or blocked jobs.
  </Card>

  <Card title="Generic webhook" icon="webhook" href="/integrations/ingestion">
    Use the Scrubbe canonical payload format to send events from any custom monitoring tool or internal system.
  </Card>
</CardGroup>

<Note>
  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](/integrations/ingestion) page for full setup instructions.
</Note>

## 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.