Docs · Integrations

Slack alerts

Channel routing per severity — critical blocks in #incidents, warnings in #infra-reviews.

Connect a webhook

DriftGuard posts review results to Slack through an incoming webhook. Create the webhook in your Slack workspace, then paste the URL into the dashboard (Settings → Slack). The URL is a secret and is stored server-side — never commit it to your repo.

Route by severity

Once connected, choose which channel receives which severity. Critical blocks can go to your incident channel while warnings stay in a quieter review channel:

.github/driftguard.yml

# .github/driftguard.yml
integrations:
  slack:
    enabled: true
    # The webhook URL itself is stored in the dashboard, not in the repo.
    routing:
      block: "#incidents"        # critical / blocked merges
      warn:  "#infra-reviews"    # warnings that still allow merge
      pass:  null                # no message on clean PRs (default)

Message shape

Each alert is a Block Kit message summarising the decision and the top findings:

slack-message.json

POST https://hooks.slack.com/services/T…/B…/…
{
  "text": "DriftGuard blocked acme/platform#482",
  "blocks": [
    { "type": "section", "text": {
      "type": "mrkdwn",
      "text": "*BLOCKED* · acme/platform#482\nPolicy: aws_rds_cluster.prod.delete\nCost: +$0/mo · Security: 0 high" } }
  ]
}

Slack notifications are optional and require dashboard setup for the webhook URL. DriftGuard is in early access.