Skip to main content
A trigger decides when an automation runs. You pick it in the Trigger card of the automation editor (“Choose what starts this automation”) by selecting a tile.

Trigger types

An automation has one trigger. To run the same task on a schedule and on an event, create two automations.

Schedules

A Scheduled trigger runs the automation at regular intervals. Set these fields: The shortest interval is 10 minutes. A one-time automation runs once at a time you choose and is then archived. You create it by asking @coderabbit in Slack, for example “tomorrow at 10am, draft an RCA for this incident in this thread”. See One-time automations.

Channel messages

A Slack message or Discord message trigger runs when a new top-level message is posted in a channel. Use it to react to repeated events, such as alerts from a monitoring bot, deployment notices, or questions in a help channel. The editor has no author field. To limit the trigger to messages from particular authors, such as your Datadog bot, ask for it when you create the automation in Slack or Discord chat. See Slack channel message triggers. Channel message automations always reply in the thread of the message that started the run, and their destination is on the same platform as the source channel. Run now isn’t available. In Discord, an automation belongs to the parent channel even when it’s created in a thread. See Slack channel message triggers and Parent-channel scope.
Every matching message starts a run that uses Agent minutes, so use Text includes or an author limit to keep routine chatter out, and see Spend limits to cap busy channels.

Webhook events

A webhook trigger runs when another tool sends an event that matches the trigger’s rules. Select the provider’s tile in the Trigger card. Paused automations ignore webhook events.

Supported providers

Provider tiles list the provider’s event types, so you can pick events instead of typing them. Custom accepts any event types you enter.

Managed webhooks

For GitHub, Jira, Linear, and PagerDuty, CodeRabbit creates the webhook in the provider and keeps it in sync with the automation. After you save, the editor confirms it, for example Jira webhook created, and no setup is needed in the provider.
  • GitHub: the trigger uses the repositories the CodeRabbit GitHub App can access, so you don’t need a personal access token. Install the CodeRabbit GitHub App on the organization and repositories you want to use, then choose the Repository and Event types, such as pull_request or issues. For pull request events, Run only when narrows the trigger to pull requests that are merged, not merged, drafts, target a base branch, or have a head branch with a given prefix, or to a custom payload field.
  • Jira: under Jira projects, keep All projects or select up to 50 projects. Project selection works with issue, comment, work log, and issue property events. With other event types, the editor shows “Project scoping isn’t available for the selected event types.” and the trigger covers all projects.
  • Linear: choose a Linear authorization, or select Connect another Linear workspace to add one. CodeRabbit keeps your draft while you authorize and returns to the editor. Under Linear teams, keep All public teams or select teams.
  • PagerDuty: the webhook subscription covers the whole PagerDuty account, not a single service or team.
Connecting a provider for managed webhooks takes a CodeRabbit admin. If the provider isn’t connected yet, the editor shows “Ask a CodeRabbit admin to connect” the provider. Once it’s connected and available to automations, anyone who can create automations can use it. The GitHub webhook admin connection can’t be used as a destination. See Connections and Base Scope. For GitHub, Jira, and Linear, the Filter row narrows the trigger to tickets with a label or status: The Create PR from Linear issue, Create PR from Jira issue, and Create PR from GitHub issue templates use this filter, so labeling a ticket is enough to start an implementation.

Other providers

For providers that CodeRabbit doesn’t manage and for Custom, save the automation first. The editor then shows Webhook endpoint created with the webhook URL, the values to configure in the provider, such as a header or secret, and setup steps for that provider. Select Reveal secrets to see secret values. Configure the webhook in the provider, then test the trigger. Reusing a webhook connection that another automation already set up requires permission to manage integrations. While another active automation uses the same connection, its shared secret can’t be changed.

Matching rules

A webhook trigger decides which events start a run with matching rules:
  • Event types: the provider events to accept, such as Issue.create for Linear or incident.triggered for PagerDuty. Add more under Advanced > Additional event types.
  • Payload conditions: checks on fields in the event’s payload, using equals, contains, starts with, exists, or a regular expression. GitHub’s Run only when filters and the ticket Filter row are payload conditions.
A trigger can have up to 25 rules, each with up to 20 conditions. An event that matches no rule doesn’t start a run. If an automation already has custom payload rules, for example from the API, the editor shows its event types read-only and keeps the rules when you save.

Deduplication

Providers sometimes deliver the same webhook event more than once. CodeRabbit deduplicates matching deliveries so a repeated event doesn’t start a second run:
  • Window: a matching delivery with the same content is ignored for 60 seconds after the first one.
  • GitHub, Linear, Jira, and PagerDuty: the same event keeps the same run identity after the window too, so redelivering it later doesn’t start another run. Changes to delivery headers alone don’t make it a new event.
  • Linear retries: CodeRabbit ignores Linear’s delivery-only webhookTimestamp field. Changing only that timestamp doesn’t create a new event; the event content must change.
A deduplicated delivery doesn’t create a run, so it doesn’t appear in the run history or in Activity. The webhook response shows what happened:
accepted and deduplicated are returned for automations that deliver to Slack or Discord. For automations without a Slack or Discord destination, the response contains only ok and matched.

Test a trigger

Follow the run on the automation’s page. If no run appears for a webhook, check that the automation is active, that the event type and conditions match, and that the delivery isn’t a repeat within the deduplication window. See Manage and monitor automations.

What’s next

Automation destinations

Choose where each run delivers its result.

Manage and monitor automations

Follow runs and check why an automation did or didn’t run.

Automation guides

See complete setups for incident response, support triage, and ticket triage.