> ## Documentation Index
> Fetch the complete documentation index at: https://docs.superlog.sh/llms.txt
> Use this file to discover all available pages before exploring further.

# Slack Integration: Superlog Incident Notifications

> Receive Superlog incident alerts and agent run results directly in Slack. Resolve incidents and leave feedback on investigations without leaving Slack.

Connecting Slack brings Superlog notifications into the channel your team already watches. When a new incident is created or an agent run completes, Superlog posts a message with the key details and a set of action buttons — so you can resolve an incident or leave feedback on the investigation without leaving Slack.

## What the Slack integration does

<CardGroup cols={2}>
  <Card title="Incident alerts" icon="bell">
    Superlog posts a message to your chosen channel the moment a new incident is detected.
  </Card>

  <Card title="Agent run summaries" icon="robot">
    When the AI agent finishes an investigation, the result — including root cause and PR link — appears in the same thread.
  </Card>

  <Card title="Resolve from Slack" icon="circle-check">
    Click the **Resolve** button directly in the Slack message. No need to open the Superlog dashboard.
  </Card>

  <Card title="Give feedback" icon="comment">
    Click **Give feedback** to leave a note on an agent run. Your input helps improve the agent's accuracy over time.
  </Card>
</CardGroup>

## How to connect

<Steps>
  <Step title="Open Settings in the Superlog dashboard">
    Navigate to **Settings** in the left sidebar of your project.
  </Step>

  <Step title="Start the Slack OAuth flow">
    Click **Connect Slack**. You will be redirected to Slack to authorise the Superlog app for your workspace.
  </Step>

  <Step title="Approve the requested scopes">
    Superlog requests the following scopes:

    | Scope               | Purpose                                             |
    | ------------------- | --------------------------------------------------- |
    | `chat:write`        | Post messages and update existing notifications     |
    | `chat:write.public` | Post to public channels without being a member      |
    | `channels:read`     | List public channels for the channel picker         |
    | `groups:read`       | List private channels you have access to            |
    | `channels:history`  | Read message history to update notification threads |
    | `groups:history`    | Read private channel history to update threads      |
  </Step>

  <Step title="Return to Superlog">
    Slack redirects you back to the dashboard. The Settings page will confirm that Slack is connected.
  </Step>

  <Step title="Choose a notification channel">
    Under **Settings → Notifications**, pick the Slack channel where you want incident alerts and agent run results to appear. You can set a different channel per project.
  </Step>
</Steps>

<Tip>
  You can post to a private channel by inviting the Superlog app to it first (`/invite @Superlog`), then selecting it in the channel picker.
</Tip>

## Interactive buttons in Slack messages

Every Slack notification from Superlog includes action buttons that let you act without opening the dashboard.

### Resolve

The **✅ Resolve** button appears on incident and agent run messages. Clicking it marks the incident as resolved immediately, closes any linked Linear tickets, and re-sends downstream webhooks. If the incident is already resolved, clicking the button refreshes those side-effects without creating a duplicate resolution.

### Give feedback

The **💬 Give feedback** button opens a short modal where you can leave a note on how the agent handled the investigation. Your feedback is surfaced to the Superlog team to help improve the agent's accuracy over time.

### Follow-up offer

After an agent run completes, Superlog may post a follow-up offer if the investigation surfaced partial information or the agent suggests a different hypothesis is worth exploring. The offer includes a **✅ Confirm** button to trigger a new agent run and a **✖ Dismiss** button to close the offer without re-running.

<Note>
  Button clicks are authenticated against the Slack signing secret. Only members of your Slack workspace can trigger actions.
</Note>

## Org-level connection

The Slack connection is shared at the **organisation** level, the same as GitHub. You connect Slack once for your org and then assign notification channels per project. If you manage multiple projects under one org, each project can route alerts to a different channel while using the same Slack app installation.

## Custom webhook delivery

If you need to send incident events to your own endpoint — a PagerDuty integration, a custom Slack app, or any other HTTP target — use Superlog's outbound webhooks instead of, or alongside, the native Slack integration. See [Webhooks](/configuration/webhooks) for the payload schema and delivery settings.

## Next steps

* Send incident events to a custom endpoint → [Webhooks](/configuration/webhooks)
* Connect Linear to create issue tickets alongside Slack alerts → [Connect Linear](/integrations/linear)