Integrations

Your repositories' news, where your team already talks

Post changes, reviews, runs, releases and deployments to your team's chat, tell Sentry what shipped, and link changes to their Linear issues. Each integration is a webhook made for its service, retried and logged like any other.

RegisterRead the docs

Chat

Slack, Discord, Microsoft Teams and Mattermost

Choose the events a channel gets: changes opened and merged, reviews completed, runs that failed (or passed, off by default), releases published, deployments finished or waiting for review. Each message says what happened and links back to it, and never holds a secret, a log line or a deployment's description.

Slack · #deploys
  • Run #41 CI failedJob failed: test (node: 24). On main at 7e4f0b1 in acme/invoices.acme/invoices · Branchscope
  • Deployment to production waiting for reviewv1.4.0 (3fb9414) in acme/invoices, set off by alice. Reviewers: bob, carol.acme/invoices · Branchscope
  • Release v1.4.0 publishedalice published it in acme/invoices.acme/invoices · Branchscope

Sentry

Sentry knows what shipped

When a release is published, Sentry gets it, with its tag as the version and its commits since the previous release, so errors link back to the commits that shipped them. When a deployment succeeds, Sentry records a deploy of that release to the environment.

acme › Integrations › Sentry
  • create the releaserelease.publishedPOST /api/0/organizations/acme/releases/
  • set its commitsrelease.publishedPUT /api/0/organizations/acme/releases/v1.4.0/
  • finalize itrelease.publishedPUT /api/0/organizations/acme/releases/v1.4.0/
  • record the deploydeployment.statusPOST /api/0/organizations/acme/releases/v1.4.0/deploys/

Linear

Changes linked to their Linear issues

Connect an organization's Linear workspace, and a change links to the issues whose keys, such as ENG-123, are in its branch, title, description or commits. Each issue gets the change and its status; owners can turn on moving issues forward and a comment with each review's counts. Linear never closes or merges a change.

acme/invoices › Changes › #12

ada/eng-123-export-invoices → main

Linear issues

  • ENG-123 Export invoices as CSVAdaIn Review
  • OPS-45, was ENG-118 Empty rows in exportsBobIn Progress

Managed by people

Webhook URLs kept secret

Repository administrators add a repository's integrations and organization owners an organization's, as do site administrators, always as people: agents and apps can't. URLs and tokens are encrypted and shown again only as their host and last 4 characters, messages go only to public HTTPS addresses, and Send test and the delivery log show how each one went.

acme/invoices › Integrations
  • Slack#deploysSend testhooks.slack.com …x7Qzrun.failed, deployment.review_requested, release.published
  • Discord#releasesSend testdiscord.com …9fA2release.published
  • SentrySend testde.sentry.io …a1b2release.published, deployment.status

Bring your repository's news to your channel

Add an integration under Settings → Integrations, choose its events, and press Send test.

Register