Skip to main content
Replicas integrates with Sentry as a public integration. Connect your Sentry organization once, and Replicas can react to Sentry events as automation triggers.

Setup

  1. Go to Organization → Integrations
  2. Find Sentry and click Install
  3. Pick your Sentry organization and approve the install
Only organization admins can manage the Sentry connection. An enabled automation needs an active Sentry connection.

Self-hosted Sentry

If you run Sentry yourself, connect it with a token instead:
  1. In Sentry, open Settings → Custom Integrations and create an internal integration with Read access to Organization, Project, and Issue & Event (org:read, project:read, event:read)
  2. In Organization → Integrations, find Sentry and click Self-hosted
  3. Enter your Sentry URL (for example https://sentry.example.com) and the integration’s token. Add its Client Secret to use automation triggers
Replicas checks the URL and token before saving. The server must be reachable from the internet over HTTPS on a public IP address. For automation triggers, open Configure, copy the webhook URL into the internal integration’s Webhook URL, and enable the issue and error webhooks. To disconnect, click Disconnect under Configure.

Disconnect or reconnect

Open Configure → Open Sentry, then uninstall Replicas from your Sentry organization’s Settings → Integrations. Replicas clears the connection when Sentry confirms removal. Return to Replicas or click Check connection to refresh its status. To reconnect, wait for Sentry’s uninstall to finish, then repeat setup from Replicas. If Sentry says already installed after an earlier disconnect, uninstall the existing installation in Sentry first.

What it enables

Once Sentry is connected, a new Sentry trigger type appears when you create or edit an automation. You can fire automations on issue alerts, new issues, or new error events, and optionally filter by Sentry project and minimum severity. See Sentry triggers for the supported events and filters.

Agent access

Workspace agents can also read Sentry through @replicas/sdk. Access uses the organization connection above and is read-only. There is no personal Sentry connection.
Pass a relative Sentry API path. Replicas supplies the credential server-side and rejects writes, absolute URLs, and oversized or slow responses. Turn the ability off per environment from the Default skills list.