Skip to main content
Automations is a workspace feature: an automation runs CodeRabbit Agent on a schedule, when a channel message arrives, or when a webhook event arrives, and delivers the result where you choose. You can create automations in the web app, through the API, or from Slack. This page covers what is specific to Slack. For how automations work on every surface, see CodeRabbit Automations. For step-by-step setups such as incident response and support triage, see Automation guides.

Create an automation from Slack

Mention @coderabbit in a channel or DM and describe the job and when it should run. For example, in #platform-eng:
Slack message
For a recurring or message-triggered automation, CodeRabbit first does the job once in the conversation as a trial. Review the output and ask for changes until it looks right. CodeRabbit then shows an Automation draft ready card that summarizes the task, when it runs, where it belongs, and where it posts. Nothing is saved or active until you confirm:
  • Create automation saves the automation, and it starts running on its trigger.
  • Edit details lets you change the draft before you save it.
  • Cancel discards the draft.
The automation belongs to the channel or DM where you created it. Results from the first run teach CodeRabbit the output you want, and later runs follow the same instructions. If your workspace limits who can create automations, people who aren’t allowed see a message such as “Only Slack workspace admins or CodeRabbit admins can create automations in this workspace.” See Who can create automations. For other ways to create automations, see Create and edit automations.

Automations slash command

Run /automations in a channel to see and manage the automations that belong to it. The command takes no extra text: use /automations or /automations help. When you start a new automation from the command, choose a starter template or Describe your own:
  • Answer product questions
  • Investigate support tickets
  • Triage engineering issues
  • Respond to incidents
  • Share customer updates
A template fills in the agent instructions and the trigger. Edit the instructions, choose whether it runs on new channel messages or on a daily or weekly schedule, pick a timezone, and select Save and activate. Describe your own starts a conversation: select Create draft, then confirm the proposed automation in the channel.
Slack doesn’t support slash commands in DMs or threads. Use /automations in a channel, or mention @coderabbit in a DM.

One-time automations

Ask for a one-time automation in Slack chat, for example:
Slack message
It runs once at the time you choose and is then archived. CodeRabbit doesn’t do a trial run first. One-time automations can only be created from Slack chat, and you can’t edit them in the web app editor or start them with Run now.

Slack channel message triggers

A Slack channel message trigger starts a run when a new top-level message appears in the automation’s channel. Use it to react to repeated events, such as alerts, deployment notices, or questions posted in a help channel. Create one by asking @coderabbit in that channel, or in the web app by choosing the Slack message trigger and a Source channel. For text filters, see Channel messages. To limit the trigger to messages from particular people, bots, or apps, name them when you ask @coderabbit, for example “only for messages from the Datadog bot.” The web app editor has no author field. CodeRabbit always replies in the thread of the message that started the run, so these automations use Same thread delivery. CodeRabbit can also respond to later replies in that thread when the instructions ask for it, for example “if someone replies fix it, open a revert PR.” Reply monitoring is off unless the instructions ask for it. The automation then wakes for every reply, or only for replies that contain the text you name (case-insensitive). CodeRabbit’s own replies don’t wake it, and a paused automation ignores replies. Run now isn’t available for these triggers. To test one, turn the automation on and post a message in the channel that matches the trigger, or start in a test channel.
Each matching message starts a run that uses Agent minutes. Give busy channels their own Automation limit, as described in Scope and spend limits.

Delivery in Slack

An automation with a Slack destination uses one of two delivery modes:
  • Fresh thread: starts a new thread for every run.
  • Same thread: posts into the same thread each time. Slack channel message triggers require it, and it’s also available when a recurring automation was created from a thread with a root message.
For a public Slack channel destination, CodeRabbit joins the channel before it posts the run, so you don’t need to invite the bot. For a private channel, run /invite @coderabbit in the channel first. Otherwise, saving the automation fails with “CodeRabbit could not post in that Slack channel.”
If the Slack workspace hasn’t granted CodeRabbit permission to join public channels, the run fails before it posts and reports a reauthorization error. A workspace admin must reauthorize the Slack integration in Connections to grant the permission.
To get results in your own DM, choose My DM with CodeRabbit as the destination in the web app editor. This destination is available for scheduled and webhook triggers, not for Slack channel message triggers. An automation you create by messaging @coderabbit in a DM belongs to that DM.

Buttons, second channel, and DMs

These options don’t have their own fields. You turn them on by describing them in the automation’s instructions, either in Slack chat or in the Agent instructions in the web app. When you save, CodeRabbit reads the instructions and sets the options up. Check the sample run in Slack, or the saved automation in the web app, to confirm they were picked up. See Write agent instructions.

Buttons

Ask for buttons by name and say what each one should do. They appear on the automation’s Slack reply. When someone selects a button, CodeRabbit runs that button’s instruction as a follow-up in the same thread. An automation can have up to 25 buttons.
Buttons appear on every reply unless the instructions say “only on the first reply.” Buttons need a Slack destination, so they can’t be added to an automation that only writes to another tool.

Second channel

An automation posts to its own channel: the one it was created in, or the destination you chose. Scheduled and message-triggered automations can also post to one fixed public channel that you name in the instructions, either every time or only when a condition is met. Each run can send up to 10 messages in total across both channels.

Direct messages

An automation can send DMs when the instructions ask for it: to you, to named people, or to people the task picks, such as the PR author. For example, “DM me if anything is Critical.” Webhook-triggered runs post only to their destinations: they can’t send these DMs or post to a second channel. To receive webhook results in a DM, choose My DM with CodeRabbit as the destination, as described in Delivery in Slack.

Scope and spend limits

An automation runs with the of its creator in the automation’s channel or DM, or of whoever selected Run now, as described in Connections and Base Scope. To see which scope applies, open Slack > Channel mappings in the web app. Automation runs use Agent minutes. In Slack > Channel mappings, each assignment has an Automation limit for automation and trigger runs, separate from the Interactive limit for runs that people start. To give a busy channel its own limit, add an assignment that covers only that channel. Requests that match more than one assignment are blocked, so narrow a broader assignment that covers the same channel and members first. See Spend controls. For other limits, see Spend limits.

Manage automations in Slack

Run /automations in a channel to list its automations. Each automation has buttons to manage it:
  • Run now starts a run right away. It’s available for active recurring schedules only.
  • Pause stops the automation from running until you select Resume.
  • Edit changes the automation.
  • Delete removes it.
Manage an automation from the channel or DM it belongs to. In a channel, any channel member can select Run now or stop a running automation. In a DM, only the creator, a Slack workspace admin, or a CodeRabbit admin can run or stop it. Editing, pausing, resuming, and deleting depend on your role. See Permissions. In the web app, Slack > Automations lists the workspace’s Slack automations. Its Prebuilt automations section has templates that post to Slack, such as Triage Linear issue, Triage Jira issue, Triage GitHub issue, and Triage PagerDuty incident. For automation details, run history, and Activity, see Manage and monitor automations.

Archival

CodeRabbit archives a Slack automation automatically when the place it belongs to becomes unavailable:
  • DM automations archive when the DM becomes unusable, the creator leaves the workspace, or the automation posts into a fixed thread with Same thread delivery and that thread’s root message disappears.
  • Channel automations archive when the channel is deleted, the bot loses access, or the automation posts into a fixed thread with Same thread delivery and that thread’s root message disappears.
  • One-time automations archive after they run.
Archived automations are different from paused automations. See Archived automations.

Automate with the API and MCP

Automate this with the CodeRabbit API and MCP server.

What’s next

CodeRabbit Automations

Learn how automations work across the web app, Slack, Discord, and the API.

Automation guides

Set up incident response, support triage, ticket triage, and more, step by step.

Connections and scopes

Control which repositories and tools automation runs can access, and set spend limits.