This article covers Phoenix Alerts, the paging and on-call product from Phoenix Incidents.

Overview

The Phoenix Alerts integration for Sentry pages your on-call team when a Sentry issue alert fires. You connect your Sentry organization to Phoenix Alerts once; after that, any alert rule with the "Send a notification via Phoenix Alerts" action creates an alert in Phoenix Alerts and pages the on-call responder for the service you choose.

Resolve status stays in sync in both directions: resolving the Sentry issue resolves the Phoenix Alerts alert, and resolving the alert in Phoenix Alerts marks the Sentry issue resolved.

What it does NOT do

Acknowledge is not synced. Acknowledging an alert in Phoenix Alerts changes nothing in Sentry. Only resolves sync — and on the Sentry side, only marking the issue resolved syncs (ignoring or assigning it does not).
Issue details are not synced. Assignee, priority, comments, and tags stay in Sentry — only resolve status flows between the two systems.
Your Sentry alert rules are never modified. You add the Phoenix Alerts action to rules yourself; Phoenix Alerts never creates or edits them.
Only issue alerts are supported. Sentry metric alerts do not page Phoenix Alerts.
One Phoenix Alerts account per installation. All alert rules in the organization page the same Phoenix Alerts account — individual rules can't use different accounts.

Prerequisites

A Phoenix Alerts account with at least one service, and access to create an API key (Configuration → API Keys in the Phoenix Alerts Jira app).
Owner or Manager permissions in your Sentry organization.

Installation

Open the Phoenix Alerts install link in your Sentry organization — from Phoenix Alerts support, or via Settings → Integrations → Phoenix Alerts → Add Installation once listed on the marketplace.
Approve the permissions on the consent screen.
Sentry redirects you to the "Connect Phoenix Alerts" page.
In another tab, open the Phoenix Alerts Jira app, go to Configuration → API Keys, and create or copy an API key.
Paste the key into the Phoenix Alerts API key field and submit.
You'll see "Setup complete — Phoenix Alerts is ready."
In Sentry, add the "Send a notification via Phoenix Alerts" action to an alert rule (see Configuration below).

The setup page expires after 3 hours (24 hours maximum). If it expires, reopen it from your Sentry installation — or reinstall if it's been more than 24 hours.

Configuration

Add the "Send a notification via Phoenix Alerts" action to each Sentry alert rule that should page Phoenix Alerts. The action has two fields:

Field	What it does
Phoenix Alerts service (required)	The Phoenix Alerts service to page. Alerts from this rule route to this service's on-call.
Severity (optional)	SEV1 (most urgent) through SEV5. If you leave it off, the severity comes from the Sentry event level (see table below)

Sentry Alert Level Mapping to Severity

If you do not specify a severity level, Phoenix Alerts will apply this mapping:

Sentry Event Level	Phoenix Severity
`fatal`	`SEV1`
`error`	`SEV2`
`warning`	`SEV3`
`info`	`SEV4`
`debug`	`SEV5`

Troubleshooting

If the service dropdown says "Complete API key setup first", this means teh installation was not completed successfully.
If the dropdown is empty, create a service in Phoenix Alerts first (or reinstall the integration).

What the alert looks like in Phoenix Alerts

Title: the Sentry issue title.
Severity: the rule's Severity, or mapped from the Sentry event level (see Configuration).
Service: the rule's Phoenix Alerts service.
Source: "Sentry", with a link back to the Sentry issue.

De-duplication

Repeat firings of the same Sentry issue update the existing open alert instead of creating a new one or paging again. If a repeat event is more severe, the alert's severity is raised.
Once the alert is resolved, the next firing of that issue creates a fresh alert.
Webhook deliveries that Sentry retries never cause duplicate alerts or duplicate pages.

Uninstall

Uninstall from Sentry under Settings → Integrations → Phoenix Alerts. After uninstalling:

Sentry alerts stop creating Phoenix Alerts alerts, and resolve sync stops in both directions.
Alerts already created are untouched — nothing is deleted or auto-resolved.
Reinstalling starts fresh: you'll complete the API-key setup again.

Troubleshooting

Symptom	What to do
The install flow ends with an error ("Sentry rejected the install" or "Phoenix Alerts is not ready to complete the install")	Retry the install from Sentry. If it keeps failing, contact Phoenix Alerts support.
"The API key you entered is not recognized."	Copy a fresh API key from Configuration → API Keys and try again.
"Your setup link expired."	Submit the form again — a fresh link is issued automatically.
"Your setup window expired. Reinstall the Phoenix Alerts integration from Sentry to start over."	Reinstall the integration from Sentry.
"This installation is already connected to a Phoenix Alerts account."	If the connected account is wrong, reinstall with the correct API key, or contact your Phoenix Alerts administrator.
A rule fires but nobody is paged, and Sentry shows no error	The API-key setup was never finished, or the key was later revoked. Redo the setup form with a valid key.
The wrong service or on-call rotation gets paged	Edit the alert rule and pick the correct Phoenix Alerts service.
The rule won't save	Phoenix Alerts service is required — pick a service.
The service dropdown says "Complete API key setup first"	Finish Installation steps 4–5.
The service dropdown is empty	Create a service in Phoenix Alerts, or reinstall the integration.
Resolving the Sentry issue didn't resolve the Phoenix Alerts alert	Only alerts created after the integration was installed sync. Resolve older alerts manually in Phoenix Alerts.
Resolving the alert in Phoenix Alerts didn't resolve the Sentry issue	Resolve the issue manually in Sentry. If it keeps happening, reinstall the integration to refresh the connection.
Sentry reports repeated webhook delivery failures, or disables the integration	Contact Phoenix Alerts support.