All Integrations
AlertingSlack App Integration

Slack Integration

Get AI-generated incident summaries, rich alert cards, and one-click actions delivered to your Slack channels. Acknowledge, snooze, or escalate incidents without ever leaving your chat.

Setup

How It Works

01

Install the TigerOps Slack App

Click "Add to Slack" from the TigerOps integrations panel. Authorize the app with your Slack workspace — no manual webhook URLs needed.

02

Choose Your Channels

Map TigerOps alert policies to specific Slack channels. Route critical incidents to #incidents, infra alerts to #ops-alerts, and budget alerts to #finops.

03

Incidents Arrive as Rich Cards

Every TigerOps incident posts a rich Slack message with severity, affected service, AI root cause summary, and action buttons — all in one card.

04

Act Without Leaving Slack

Acknowledge, snooze, escalate, or run AI-suggested remediation directly from Slack buttons. TigerOps reflects the action in real time.

Capabilities

What You Get Out of the Box

AI-Generated Incident Summaries

Every Slack incident card includes a one-sentence AI summary: what broke, what the impact is, and what the likely cause is — before a human investigates.

Rich Incident Cards

Incident severity, affected services, metric sparklines, trace links, and a direct link to the TigerOps investigation timeline — all in a single Slack message.

In-Slack Acknowledgment

Engineers can acknowledge, assign, or snooze incidents with one click inside Slack — no need to open TigerOps to act on low-priority alerts.

Alert Digest Mode

Instead of individual alert messages, TigerOps can post a daily digest to a channel summarizing all alert activity — reducing notification volume during quiet periods.

Resolve Notifications

When TigerOps auto-resolves an incident (or a human closes it), the original Slack message is updated with the resolution summary and duration.

Per-Team Routing

Route alerts by service, team tag, or environment to different channels. Infrastructure alerts go to ops, app errors go to the app team, all in one config.

Configuration

Alert Policy Routing

Configure alert policies to route to specific Slack channels based on severity and team.

alert-policy.yaml
# TigerOps Alert Policy — Slack Routing
# Configure via UI or push via the TigerOps API

alert_policies:
  - name: "Critical Incidents"
    severity: [critical]
    conditions:
      - type: ai_anomaly
      - type: slo_breach
    notification_channels:
      - type: slack
        channel: "#incidents"
        mention: "@oncall"
        include_ai_summary: true
        include_runbook: true
      - type: pagerduty
        service_key: "${PAGERDUTY_SERVICE_KEY}"

  - name: "Infrastructure Warnings"
    severity: [warning]
    tags:
      team: infrastructure
    notification_channels:
      - type: slack
        channel: "#ops-review"
        include_ai_summary: true
        digest_mode: true  # Group into hourly digests

  - name: "App Error Spikes"
    severity: [warning, critical]
    tags:
      team: app
    notification_channels:
      - type: slack
        channel: "#app-errors"
        include_trace_link: true
FAQ

Common Questions

Does TigerOps support Slack Incoming Webhooks or the Slack API?

TigerOps uses the native Slack app (OAuth) rather than incoming webhooks. This allows interactive buttons (acknowledge, escalate, snooze) to work directly in Slack. Incoming webhook mode is available as a fallback for workspace restrictions.

Can I route different alert severities to different Slack channels?

Yes. In TigerOps alert policies, you can configure separate Slack channels per severity level — critical alerts go to #oncall, warnings go to #ops-review, and informational alerts go to #monitoring-digest.

Will TigerOps spam my Slack with duplicate alerts?

No. TigerOps groups related alerts into a single incident and posts one Slack message per incident. Subsequent related alerts update the existing message rather than posting new ones. Alert suppression and deduplication are automatic.

Can engineers acknowledge incidents from Slack?

Yes. The Slack incident card includes action buttons: Acknowledge (assigns to the clicking user), Snooze (suppresses notifications for a configurable duration), Escalate (pages the on-call via PagerDuty or Opsgenie), and View in TigerOps.

Does the Slack integration work with private channels?

Yes, as long as the TigerOps Slack app is invited to the private channel. You can use /invite @tigerops in any private channel you want to receive alerts in.

Get Started

Bring AI Incident Intelligence to Slack

No credit card required. One-click Slack install. Rich incident cards immediately.