Skip to main content
Automations let CodeRabbit Agent run recurring or event-driven tasks for you from Slack. They can run on a recurring schedule, react to top-level channel messages, or run from a saved trigger such as a webhook event. You can create scheduled automations from Slack and inspect them in the web app. The web app also includes a Triggers tab for creating and managing trigger-based automations. Each automation runs under the that applies to the channel or DM where it lives, so it only accesses the repositories, connections, and spend limits that surface is allowed to use.

​
Examples

A platform team wants CodeRabbit Agent to check for new security advisories every morning. An engineer goes to #platform-eng and sends:
@coderabbit Check for new dependency vulnerabilities in the main branch
and summarize anything critical. Run this daily.
CodeRabbit Agent runs it once as a trial. After reviewing the output, the engineer confirms the automation. From that point on, a fresh thread appears in #platform-eng every morning with the results.

​
Creating an automation

Ask @coderabbit to create an automation in any channel or DM. CodeRabbit Agent walks you through the setup in a thread. When you create an automation, it runs once as a trial before activating it, so you can review the output and iterate on the prompt before it starts running on its own.
In channels, you can also use the /automations slash command as a shortcut. Slash commands are not available in Direct Messages or threads.
Any linked workspace user can create automations. Broader management remains permission-based: workspace admins can manage every automation and trigger, Automation admins can manage same-workspace automations when Automation admin management is enabled, and other users can manage the automations they created. Every automation is bound to the channel or DM where it was created, and that binding cannot be changed. If the target surface changes, create a new automation in the new place.

​
Schedules

Recurring automations can run:
  • Every x minutes (10 minutes minimum)
  • Hourly
  • Daily
  • Weekly
  • Monthly, on a selected day of the month
All schedules are timezone-aware.

​
Triggers

Triggers are rules that start CodeRabbit Agent when a matching event arrives. Open Automations > Triggers in the web app to create, edit, pause, or delete triggers. When you create a trigger, you can save it as a paused draft or save and enable it immediately. A paused trigger keeps its configuration but does not process new events until you enable it. Existing triggers can be switched between active and paused before saving changes. Each trigger has:
  • Source: where the event comes from
  • Matching rules: which events should run the trigger
  • Agent instructions: what CodeRabbit Agent should do when the trigger runs
  • Destination: where CodeRabbit Agent posts the result

​
Slack channel messages

Slack channel message triggers run when a new top-level bot or app message appears in a selected channel. Instead of waiting for a clock-based schedule, they fire when a matching message arrives. Use them when you want CodeRabbit Agent to react to repeated operational events, such as new alerts, queue-health posts, or deployment notices. Slack channel message triggers support:
  • All new top-level bot or app messages in the channel
  • A required Bot name field that identifies the Slack bot CodeRabbit should respond to, such as datadog
  • Text filters using case-insensitive substring matching
CodeRabbit Agent always replies in the triggering thread. In the current version, these triggers must use Same thread delivery. Human-authored messages never fire this trigger type. A Slack channel message trigger only runs when a new top-level message comes from a bot or app whose name matches the trigger’s Bot name field. Run now is also unavailable for these triggers. To test one, post a matching message in the channel from that bot or app.

​
Webhook events

Webhook triggers run when an external service sends a matching webhook event:
  • Any service can be connected via a custom webhook
  • Natively supported providers (with pre-configured event types and payload schemas): Datadog, Sentry, PagerDuty, Linear, Jira, Fin (formerly Intercom), Zendesk, and Pylon
After saving a webhook trigger, CodeRabbit shows the webhook URL, required header, and sample payload to configure in the source service. Webhook events are processed only when the trigger is active. Webhook triggers can match by provider event type, by JSON payload fields, or both. If no matching rule passes, the event is dropped.

​
Delivery

Each automation uses one of two delivery modes:
  • Fresh thread: starts a new thread for every run
  • Same thread: posts into the same thread each time (required for Slack channel message triggers, and also available when a recurring automation was created from a thread with a concrete root message)

​
Who can manage automations

ActionCreatorWorkspace adminAutomation adminOther channel members
Edit, pause, resume, or deleteYesYesYes, when Automation admin management is enabledNo
Run immediately (recurring only)YesYesYes (channels only)Yes (channels only)
Stop a running automationYesYesYes (channels only)Yes (channels only)
Automations in DMs can be edited, paused, resumed, or deleted by the creator, a workspace admin, or an Automation admin when Automation admin management is enabled. Stopping a running DM automation is limited to the creator or a workspace admin. Other users cannot run or stop DM automations. Slack channel message automations cannot be run manually. To test one, post a matching message in the channel from the configured bot or app.

​
Archival

Automations are archived automatically when their place becomes unavailable:
  • DM automations archive when the DM becomes unusable, the creator leaves the workspace, or the required same_thread root message disappears.
  • Channel automations archive when the channel is deleted, the bot loses access, or the required same_thread root message disappears.
Archived automations are distinct from paused automations and cannot be resumed.

​
Viewing automations in the web app

The Automations page in the web app is available to all workspace users. It shows which channels have active automations, their triggers, delivery mode, and recent run history. Run entries link to thread reviews when available. Workspace admins can see every automation and trigger in the workspace. Automation admins can see and manage same-workspace automations when Automation admin management is enabled. Other users can see automations and triggers they created. Available actions depend on your permissions and the automation type.

​
What’s next

Scopes

Control which repositories and tools automation runs can access.

Thread reviews

Inspect the output of an automation run.

Usage

Review activity after automations run.