# Slack

The Slack integration makes Slack a delivery destination for the alerts and reports that Revenium already generates. Once connected, alerts configured under [Set Budgets & Alerts](/track-and-control-costs/set-budgets-and-alerts.md) can be routed to Slack channels rather than (or alongside) email and webhooks.

Slack is managed under **Integrations > Slack and GitHub** in the product, alongside the GitHub integration. Each integration shows its connection status, credentials, and configuration on the same screen, and either can be connected, reconfigured, or disconnected without affecting the other.

{% hint style="info" %}
For GitHub Copilot and AI coding assistant cost tracking, see [GitHub Integration](/track-and-control-costs/analyze-ai-tooling-spend/github-integration.md).
{% endhint %}

### <i class="fa-slack">:slack:</i> Routing Alerts and Reports

#### What's Configurable

The integration page shows the number of Slack channels currently configured. The **Manage** button opens the channel configuration, where channels are mapped to alerts and reports.

For most teams, the right pattern is one channel per concern: a `#ai-cost-alerts` channel for spend guardrails, a `#ai-incidents` channel for failure-rate or anomaly alerts, and possibly a `#ai-reports` channel for weekly or monthly summaries. Channel-per-concern keeps notifications scoped to people who actually need to see them rather than dumping everything into one general channel where it gets ignored.

#### Why Slack Specifically

Slack is the channel most teams already live in for operational decisions. An AI cost spike that hits the right Slack channel five minutes after it happens lands in front of an engineer who can investigate; the same spike sitting in an inbox might not get noticed for a day. The integration exists to close that latency gap.

Webhooks (covered on the Set Budgets & Alerts page) cover everything Slack doesn't — incident management tools, custom routing logic, automated circuit-breaking. Email is always available without configuration. Slack sits between them: more immediate than email, less custom than a webhook, and tuned to the conversation patterns most teams already have.

### <i class="fa-plug">:plug:</i> Connecting and Managing the Integration

The Slack integration follows a standard lifecycle on the Slack and GitHub tab:

* **Connect** the integration with a Slack workspace authorisation
* **Validate** the connection — the integration shows its last successful validation timestamp on the configuration screen, and re-validates on each sync
* **Sync** — Slack channel updates happen as you change them in Slack
* **Reconfigure or disconnect** at any time from the same screen

Disconnecting Slack doesn't affect the GitHub integration on the same tab, and reconnecting after a disconnect resumes data flow without requiring any backfill on your part.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.revenium.io/integrations/slack.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.