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

# Answer code and product questions in Slack

> Set up a CodeRabbit automation that answers each question posted in a Slack channel with a short answer and links to the code, pull requests, or docs it used.

Cloud Only (This feature is available on CodeRabbit Cloud only. It is not available on self-hosted CodeRabbit deployments.)

## What you get

CodeRabbit answers each question posted in a channel such as `#ask-eng` with a short answer and links to the code, pull requests, or docs it used. When evidence is missing or conflicting, it says so and asks one focused question. It skips unrelated posts and questions already answered in the thread, and it doesn't treat a merged change as released.

For occasional questions, you don't need an automation: mention `@coderabbit` in any channel.

## Before you start

| Requirement | Who does it | Where |
| - | - | - |
| Your repositories as connections. Add Notion, Google Drive, Linear, Jira, or an [MCP server](https://docs.coderabbit.ai/connections/mcp-servers.md) if answers depend on specs or known issues. | A CodeRabbit admin | [Connections](https://docs.coderabbit.ai/connections.md) |
| A scope for the channel, if it should use fewer repositories or connections than the rest of the workspace | A CodeRabbit admin | **Slack** > **Channel mappings** |
| An **Automation limit** for the channel | A CodeRabbit admin | **Slack** > **Channel mappings** |
| CodeRabbit in the channel, if it's private | A channel member | `/invite @coderabbit` in the channel |

Every question starts a run that uses Agent minutes, billed like CodeRabbit Agent for Slack. See [Scope and spend limits](https://docs.coderabbit.ai/slack-agent/automations.md#scope-and-spend-limits).

## Set it up

**1. Open the template**

In the channel, run `/automations` and start a new automation. In **Purpose**, choose **Answer product questions**. In **When to run**, choose **New channel message**.

**2. Check the instructions and connections**

Edit the **Agent instructions** if answers should stick to some repositories or docs. Check that **Connections Available** lists what the answers need.

**3. Save**

Select **Save and activate**. The automation is active right away, without a trial run.

## Test it

Post a question in the channel that your code or docs can answer, as a new top-level message. Thread replies don't start a run. **Run now** isn't available for message triggers.

## Check the runs

CodeRabbit replies in the thread of each question. Each run is also listed on the automation's page. See [Automation details](https://docs.coderabbit.ai/automations/manage.md#automation-details).

If answers miss context, teach CodeRabbit your team's facts with `@coderabbit remember` in a thread. See [Knowledge Base](https://docs.coderabbit.ai/slack-agent/knowledge-base.md).

## Variations

* **One run a day.** To spend less in a busy channel, choose **Daily schedule** in **When to run**, with a **Time** and **Timezone**. Each run reviews the questions left unanswered in the last 25 hours.
* **Follow-up replies.** Ask in the instructions to answer follow-up replies in the thread. See [Slack channel message triggers](https://docs.coderabbit.ai/slack-agent/automations.md#slack-channel-message-triggers).

## What's next

> [card] [Automations in Slack](https://docs.coderabbit.ai/slack-agent/automations.md)
>
> Learn how channel message triggers and thread replies work.

> [card] [Knowledge Base in Slack](https://docs.coderabbit.ai/slack-agent/knowledge-base.md)
>
> Save team facts that every answer can use.

> [card] [Share customer updates](https://docs.coderabbit.ai/automations/guides/share-customer-updates.md)
>
> Post a weekly summary of customer-visible changes.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.