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

# Slack

> Run Orbitrage from Slack — onboard, create projects and keys, ask analytics, and get proactive alerts.

The Orbitrage Slack app is a **full agent**, not just a notifier. Once a workspace is connected, your team can do almost everything from Slack — onboard, create projects and API keys, ask any cost/usage/anomaly question (with charts), and get proactive incident and anomaly alerts. **Most users never open the dashboard.**

<CardGroup cols={2}>
  <Card title="Ask anything" icon="comments">
    `@Orbitrage what's our spend this week?` — answers in-thread with a takeaway and a chart image.
  </Card>

  <Card title="Do anything" icon="wand-magic-sparkles">
    "Create a project called Prod", "mint an API key", "set an alert on cost" — executed from Slack (with a confirm step).
  </Card>

  <Card title="Get alerted" icon="bell">
    Proactive messages when your first workflow goes live and when anomalies are detected — no setup beyond connecting.
  </Card>

  <Card title="Onboard" icon="rocket">
    A guided card walks a new workspace from zero to a working API key and integration snippet.
  </Card>
</CardGroup>

<Frame caption="Ask the Orbitrage agent anything in a thread — it answers in-thread with a takeaway and a rendered chart.">
  <img src="https://mintcdn.com/orbitrage/nK2Q4BMDsPhLiujI/slack_agent.png?fit=max&auto=format&n=nK2Q4BMDsPhLiujI&q=85&s=7d7d7c6fd57eb166ae3f9c108bae607e" alt="Orbitrage Slack agent answering a tools-and-costs question with a chart" width="917" height="926" data-path="slack_agent.png" />
</Frame>

## What you can do from Slack

<AccordionGroup>
  <Accordion title="Onboarding — go from zero to a live key">
    DM the bot for an onboarding card. *Create my first project* → a modal → your API key plus an integration guide arrive in the DM (the key is shown once, ephemerally). The App Home tab is a persistent starting point.
  </Accordion>

  <Accordion title="Analytics — ask any question, get a chart">
    Mention the bot or DM it: "cost trend last 7 days", "top models by spend", "which workflow errors most", "anomalies today". You get a text takeaway plus a rendered PNG chart in the thread. Same engine as [Ask Analytics](/platform/ask-analytics).
  </Accordion>

  <Accordion title="Admin — create projects, keys, and alerts">
    "create a project called Prod", "create an API key for Prod", "alert me when cost goes over \$50/day". Each write shows a **Confirm** button first; on confirm, the bot executes it and delivers any secret (like a minted key) ephemerally.
  </Accordion>

  <Accordion title="Deep dives — background root-cause briefs">
    "deep dive on what's wrong" kicks off a background investigation that posts a root-cause brief (and reports) back into the thread when ready.
  </Accordion>

  <Accordion title="Slash command — answers in your DM">
    `/orbitrage <question>` works from anywhere, even channels the bot isn't in — the answer arrives in your DM.
  </Accordion>
</AccordionGroup>

## Permissions

* **Anyone** in the workspace can ask read-only analytics questions.
* **Only the installer** can create, mint, or delete. Those actions run as the installer's Orbitrage account, and every write requires an explicit **Confirm** click. A non-installer asking for a write is politely refused.

## Connect a workspace

<Steps>
  <Step title="Install the app">
    From the dashboard's **Customise → Slack** section, click to install and authorize the Orbitrage Slack app into your workspace via OAuth.
  </Step>

  <Step title="A channel is set up for you">
    On install, the bot creates (or joins) an `#orbitrage-alerts` channel and sends a welcome message. If it can't, it DMs the installer with next steps.
  </Step>

  <Step title="Start talking to it">
    DM the bot, `@mention` it in a channel, or use `/orbitrage`. That's the whole setup.
  </Step>
</Steps>

## Proactive alerts

With no further configuration, the Slack agent will:

* announce when your **first workflow goes live** (your first real LLM call), and
* post **anomaly alerts** when traffic deviates from its baseline (the detection in [the Intelligence layer](/concepts/intelligence)).

These run on a lightweight monitor every few minutes. You can also wire up explicit [webhook/Slack alerts](/platform/alerts) for specific metric thresholds.

## Two ways to send to Slack

Beyond the agent, Slack is also a delivery target for alerts:

| Method                          | Set where                                                     | Used by                                              |
| ------------------------------- | ------------------------------------------------------------- | ---------------------------------------------------- |
| **Connected app** (recommended) | Customise → Slack (OAuth)                                     | The agent, onboarding, proactive alerts.             |
| **Per-org webhook**             | Customise → Slack integration (paste an incoming-webhook URL) | The `send_to_slack` analytics tool and anomaly cron. |
| **Per-alert webhook**           | The `webhook_url` of any alert                                | That specific alert (auto-formatted as Block Kit).   |

<Note>
  Disconnecting from **Customise → Slack** revokes the bot token and removes the installation. Read-only analytics never expose secrets; minted keys are always delivered privately (ephemerally) to the installer.
</Note>