Skip to main content
Automations let CodeRabbit Agent run recurring or event-driven tasks for you. 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 and edit scheduled automations in the web app automation editor, or create them conversationally from Slack. 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 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

Create a scheduled automation in the web app automation editor, or ask @coderabbit to create one in any channel or DM. In Slack, CodeRabbit Agent walks you through the setup in a thread. When you create an automation conversationally, 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. Edited automation prompts and new scheduled automations can be saved directly from the web app. You do not need to start a Slack or Discord conversation just to schedule an automation or update its prompt.
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.

​
Schedules

Recurring schedules are configured in the automation editor. Depending on the frequency you choose, schedule controls include interval, time, timezone, weekdays, and day of month. Recurring automations can run:
  • Every x minutes (10 minutes minimum)
  • Hourly
  • Daily at a selected time
  • Weekly on selected weekdays
  • 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. When you create an automation, you can save it as a paused draft or save and enable it immediately. A paused automation 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 automation 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, including invoking an existing durable skill so recurring or triggered runs reuse an established procedure
  • 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
Providers with managed webhook connections, such as PagerDuty, let CodeRabbit provision and synchronize the provider’s webhook subscription automatically. Managed PagerDuty webhooks support both Slack and workspace automations. The subscription is account-wide rather than scoped to a single PagerDuty service or team, and a global admin must connect PagerDuty. See Connections for setup and permissions. Linear also uses a managed webhook connection. After you connect a Linear authorization with the required access, CodeRabbit automatically provisions and maintains the Linear webhook subscription. In the automation editor, select an existing Linear authorization or choose Connect another Linear workspace to add one. CodeRabbit preserves the automation draft during the OAuth handoff and returns to the editor with the new authorization selected. Webhook administration requires Linear read, write, and admin access. These authorizations are used only to administer triggers and are not available as destination connections. See Connections for setup and permissions. For custom webhooks and providers without a managed webhook connection, CodeRabbit shows the webhook URL, required header, and sample payload to configure in the source service after you save the trigger. 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)

​
Deduplication

Webhook-triggered automations deduplicate repeated deliveries when the complete payload is byte-for-byte identical. A repeated delivery can match a trigger rule but still be intentionally ignored instead of starting another run.
  • Window: Identical payloads are deduplicated for 1 minute.
  • Trigger another run: Include a varying field, such as a timestamp, to make otherwise-identical payloads unique.
Deduplicated webhook deliveries return counters that distinguish matching events from accepted runs:

​
Who can manage automations

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.

​
Managing automations in the web app

The Automations page in the web app is available to all workspace users. It lets you create and edit scheduled automations, manage triggers, review delivery mode and inspect recent run history. 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.

Agent skills

Reuse established procedures in automation runs.