> ## 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.

# Automation guides

> Step-by-step setups for common CodeRabbit automations: incident response, Linear issue to pull request, ticket triage, support triage, Slack questions, and customer updates.

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

Each guide sets up one automation, most of them from a template that CodeRabbit ships, then shows how to test it and what its runs should produce. Some templates create automations that live in a Slack channel and run on new messages or on a schedule. Others start from a webhook event in PagerDuty, Datadog, Linear, Jira, or GitHub. A template fills in the trigger, the agent instructions, and the destination; edit the instructions to fit your team.

## Pick a guide

> [card] [Respond to incidents](https://docs.coderabbit.ai/automations/guides/respond-to-incidents.md)
>
> Get an assessment of each new Datadog, PagerDuty, or Slack alert: real or noise, recent changes, and the next step.

> [card] [Linear issue to pull request](https://docs.coderabbit.ai/automations/guides/linear-issue-to-pull-request.md)
>
> Label a Linear issue and get a pull request with the fix, linked back on the issue.

> [card] [Triage engineering tickets](https://docs.coderabbit.ai/automations/guides/triage-engineering-tickets.md)
>
> Get the likely cause and a suggested fix for each new Linear, Jira, or GitHub issue.

> [card] [Triage support tickets](https://docs.coderabbit.ai/automations/guides/triage-support-tickets.md)
>
> Get a summary, a classification, and a draft reply in Slack for each new Zendesk, Intercom, or Pylon ticket.

> [card] [Answer questions in Slack](https://docs.coderabbit.ai/automations/guides/answer-questions-in-slack.md)
>
> Answer each question posted in a Slack channel, with links to the code, pull requests, or docs used.

> [card] [Share customer updates](https://docs.coderabbit.ai/automations/guides/share-customer-updates.md)
>
> Post a weekly summary of customer-visible changes in Slack, with a sentence Support can use for each.

In the web app, templates that write back to the tool, such as a comment on a Linear issue, are on **Automations** > **Home** under **Templates**. Templates that post to a channel are under **Slack** > **Automations** > **Prebuilt automations**, and under **Discord** > **Automations** for Discord. See [Create an automation in the web app](https://docs.coderabbit.ai/automations/create.md#create-an-automation-in-the-web-app). You can also start from `/automations` in the Slack channel where the automation should post. See [Automations slash command](https://docs.coderabbit.ai/slack-agent/automations.md#automations-slash-command).

## Before you start

Each guide lists what it needs. These apply to all of them:

| Requirement | Who does it | Where |
| - | - | - |
| Agent billing. Automations aren't part of a plan; runs use Agent minutes. Automations without a Slack or Discord destination need the Automations Agent trial or paid Agent access. Slack and Discord destinations are billed like CodeRabbit Agent there. See [Who can use Automations](https://docs.coderabbit.ai/automations.md#who-can-use-automations). | A CodeRabbit admin | **Automations Agent usage** card on the Automations page, or **Billing** |
| Connected tools, such as Linear, Jira, or PagerDuty. Once connected, any member can use them. | A CodeRabbit admin | [Connections](https://docs.coderabbit.ai/connections.md) |
| The connection in the run's scope: Base Scope or the automation's agent scope for automations created on the Automations page, the creator's channel scope for automations that live in a Slack channel. See [Connections and Base Scope](https://docs.coderabbit.ai/automations/destinations.md#connections-and-base-scope). | A CodeRabbit admin | [Scopes](https://docs.coderabbit.ai/connections/scopes.md), or **Slack** > **Channel mappings** |
| The CodeRabbit GitHub App on the repositories that runs read or write. See [Identity for changes](https://docs.coderabbit.ai/automations/destinations.md#identity-for-changes). | A GitHub organization owner | GitHub |
| CodeRabbit in private Slack channels | A channel member | `/invite @coderabbit` in the channel |

Any workspace member can create automations on the Automations page. A Slack workspace or Discord server can limit who creates automations there. See [Who can create automations](https://docs.coderabbit.ai/automations/create.md#who-can-create-automations).

## Tune any automation

* **Teach it your team's facts.** Reply in a thread with `@coderabbit remember` and the fact, such as who owns a service or what customers call a feature, or run `/learn` in the channel. Facts saved in public channels are shared across the workspace. See [Knowledge Base](https://docs.coderabbit.ai/slack-agent/knowledge-base.md).
* **Reuse a procedure.** Ask CodeRabbit to save a good run's steps as a [skill](https://docs.coderabbit.ai/agent/skills.md), and name the skill in the instructions.
* **Add buttons, a second channel, or DMs.** Describe them in the instructions, for example an **Open revert PR** button or "If the verdict is Real, also post a summary to #incidents." Webhook-triggered runs can't post to a second channel or send DMs. See [Buttons, second channel, and DMs](https://docs.coderabbit.ai/slack-agent/automations.md#buttons-second-channel-and-dms).
* **Keep working in the thread.** A channel message automation can respond to later replies in its thread when the instructions ask for it, for example "if someone replies *fix it*, open a revert PR." See [Slack channel message triggers](https://docs.coderabbit.ai/slack-agent/automations.md#slack-channel-message-triggers).

## What's next

> [card] [Create and edit automations](https://docs.coderabbit.ai/automations/create.md)
>
> Build an automation from scratch in the web app, from chat, or with the API.

> [card] [Automation triggers](https://docs.coderabbit.ai/automations/triggers.md)
>
> Choose between schedules, channel messages, and webhook events.


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