> For the complete documentation index, see [llms.txt](https://docs.darcyiq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.darcyiq.com/build/integration-overview/enterprise/slack.md).

# Slack

Put Darcy in your Slack workspace, and let Darcy search, read, and post in Slack on your behalf

Slack connects to DarcyIQ in two directions, and they're worth keeping straight:

* **Darcy in Slack** — an organization connects its Slack workspace, and Darcy becomes a participant there. Mention `@DarcyIQ` in a channel, DM it, or use its slash commands.
* **Slack in Darcy** — each person connects their own Slack account, and Darcy can search channels, read threads, and post **as that person** from chat, agents, and workflows.

{% hint style="success" %}
**Both directions in one day**: An admin connects the workspace, so the team can ask Darcy questions in `#deal-desk` without leaving Slack. A rep separately connects their own Slack account, so when they ask Darcy in DarcyIQ to *"check what customer-success said about the Acme rollout and post a summary back,"* it can do both halves.
{% endhint %}

## Darcy in Slack (Organization)

### Connecting the Workspace

The **Slack Workspace** card lives in **Settings → User Configuration → Organization → Integrations**. Connecting requires organization-settings permission, so this is an admin task.

{% stepper %}
{% step %}
**Open the Slack Workspace card** Under the Organization tab, expand **Integrations**. The card explains what connecting does: the Darcy bot is installed in your workspace, your team can mention `@DarcyIQ`, and members can link their accounts.
{% endstep %}

{% step %}
**Click Connect Slack Workspace** Slack's authorization screen opens in a popup. Approve the bot's scopes and you're connected.
{% endstep %}

{% step %}
**Ask your team to link their accounts** Each person links their own Slack account in **Personalization → Connected Accounts**. Until they do, Darcy can't tell who is talking to it — it replies with a link to the page instead of an answer.
{% endstep %}
{% endstepper %}

### What Darcy Can Do in Slack

| Surface               | Behavior                                                                       |
| --------------------- | ------------------------------------------------------------------------------ |
| **Channel mentions**  | Mention `@DarcyIQ` in any channel it's in and it answers in thread             |
| **Direct messages**   | DM the bot for a private conversation                                          |
| **Assistant threads** | Slack's assistant panel, for a side conversation that doesn't fill the channel |
| **Slash commands**    | Configuration and TestDrive triage, without leaving Slack                      |

### Slash Commands

| Command                   | What it does                                                                                                                                           |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **`/darcy help`**         | Lists the available commands. This is also what a bare `/darcy` shows                                                                                  |
| **`/darcy integrations`** | Opens a **Configure Tools** modal to choose which of your integrations Darcy may use in Slack threads. `/darcy-integrations` does the same thing       |
| **`/darcy triage`**       | Reports a product issue to [TestDrive](/build/testdrive.md), which investigates it and replies in the thread. Only available when TestDrive is enabled |

{% hint style="info" %}
**Tool choices made in Slack apply to Slack.** What you enable with `/darcy integrations` governs the threads where you mention `@DarcyIQ` — it doesn't change your setup inside DarcyIQ.
{% endhint %}

Two things stop a slash command before it runs, both with a private reply explaining why: the workspace isn't connected, or your Slack account isn't linked to DarcyIQ.

### Using Your Own Slack App

Most organizations use the shared DarcyIQ Slack app. If your security policy requires the app to live in your own Slack estate, expand **Use your own Slack app** on the same card and register one:

| Field              | Where it comes from                     |
| ------------------ | --------------------------------------- |
| **App ID**         | Your Slack app's Basic Information page |
| **Client ID**      | Basic Information → App Credentials     |
| **Client Secret**  | Basic Information → App Credentials     |
| **Signing Secret** | Basic Information → App Credentials     |

DarcyIQ gives you a **manifest to download** and a link to create the app in Slack, so the scopes and endpoints are right the first time. Secrets are write-only after saving — you can replace them, never read them back.

{% hint style="warning" %}
**Registering the app is only half of it.** With custom credentials saved but the workspace never connected, Slack can reach DarcyIQ but DarcyIQ has no bot token to reply with, so mentions and DMs go unanswered. The card says so directly — *"Your custom Slack app is registered, but the workspace isn't connected yet"* — and the fix is **Connect Slack Workspace**. If you switch apps, you'll also be asked to disconnect and reconnect, because the workspace is still connected through the old one.
{% endhint %}

### Maintenance

| Situation               | What you see                                                                                                                       |
| ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| **Missing permissions** | **Reconnect required** / **Update Slack permissions** — Slack added a scope the bot needs, so reconnect                            |
| **Disconnecting**       | Removes the bot token so Darcy stops replying. It does **not** uninstall the app from Slack — do that in Slack if you want it gone |

## Slack in Darcy (Personal)

Connect your own Slack account from **Personalization → Connected Accounts**, or from the integration catalog, where it appears as **Slack**. It's an OAuth connection with no credentials to copy, and one authorization does two jobs: it links your identity for the Slack bot, and it gives Darcy Slack tools that act as you.

{% hint style="info" %}
**The personal Slack integration is in Beta.**
{% endhint %}

### What Darcy Can Do as You

| Kind                | Examples                                                                                                   | Approval           |
| ------------------- | ---------------------------------------------------------------------------------------------------------- | ------------------ |
| **Read and search** | Find channels, read a channel or a thread, search public or private messages you can see                   | Runs directly      |
| **Write**           | Send a message or a draft, schedule a message, add a reaction, create a channel, create or update a canvas | **Asks you first** |
| **Files**           | Upload a file to a channel or thread                                                                       | **Asks you first** |

Reading happens without ceremony; anything that other people would see asks for your confirmation before it goes out. Available tools depend on the scopes you approve during authorization, so a narrower grant means fewer capabilities.

These tools are available in [Chat](/core-features/darcy-chat.md), to [Agents](/core-features/agents.md), and inside [Workflows](/build/ai-workflows.md) — so "summarize the week in `#support` and post it to `#leadership` every Friday" is a [scheduled agent](/build/automations.md), not a chore.

Disconnecting the integration also removes the identity link used by the Slack bot.

## Availability

| Surface             | Requirement                                                                        |
| ------------------- | ---------------------------------------------------------------------------------- |
| **Darcy in Slack**  | Enabled for your organization, plus organization-settings permission to connect it |
| **Personal Slack**  | Enabled for your organization; then it's yours to connect                          |
| **`/darcy triage`** | TestDrive enabled, and view access to the TestDrive workspace you pick             |

If a surface isn't enabled for your organization, it doesn't appear rather than failing — check with your administrator.

## Limits and Caveats

| Consideration                   | Detail                                                                                          |
| ------------------------------- | ----------------------------------------------------------------------------------------------- |
| **Account linking is required** | The bot can't act for someone it can't identify. Unlinked users get pointed at the linking page |
| **Modal list sizes**            | The integration and workspace pickers in Slack modals list up to 100 entries                    |
| **Triage uploads**              | Video evidence attached to a triage thread is capped at 10 MB                                   |
| **Scope-dependent tools**       | Personal Slack capabilities follow the OAuth scopes you granted                                 |
| **Ticket automation**           | Triage doesn't create or update Jira or Linear tickets today                                    |

## Next Steps

| Goal                                     | Documentation                                                             |
| ---------------------------------------- | ------------------------------------------------------------------------- |
| Report and investigate issues from Slack | [TestDrive](/build/testdrive.md)                                          |
| See every available integration          | [Integration Catalog](/build/integration-overview/integration-catalog.md) |
| Control which tools agents may use       | [Tool Permissions](/build/integration-overview/tool-permissions.md)       |
| Work with Darcy in the product           | [Chat](/core-features/darcy-chat.md)                                      |
| Put a Slack summary on a schedule        | [Events & Scheduling Agents](/build/automations.md)                       |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.darcyiq.com/build/integration-overview/enterprise/slack.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.