Skip to main content
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

Respond to incidents

Get an assessment of each new Datadog, PagerDuty, or Slack alert: real or noise, recent changes, and the next step.

Linear issue to pull request

Label a Linear issue and get a pull request with the fix, linked back on the issue.

Triage engineering tickets

Get the likely cause and a suggested fix for each new Linear, Jira, or GitHub issue.

Triage support tickets

Get a summary, a classification, and a draft reply in Slack for each new Zendesk, Intercom, or Pylon ticket.

Answer questions in Slack

Answer each question posted in a Slack channel, with links to the code, pull requests, or docs used.

Share customer updates

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. You can also start from /automations in the Slack channel where the automation should post. See Automations slash command.

Before you start

Each guide lists what it needs. These apply to all of them: 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.

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.
  • Reuse a procedure. Ask CodeRabbit to save a good run’s steps as a skill, 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.
  • 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.

What’s next

Create and edit automations

Build an automation from scratch in the web app, from chat, or with the API.

Automation triggers

Choose between schedules, channel messages, and webhook events.