Phoenix Incidents for Slack

Connect your Jira-first incident workflows to Slack*. Phoenix Incidents for Slack delivers interactive messages, critical-step reminders, and a /phoenix command so responders can act without leaving Slack.

New to Phoenix Incidents? Start with What is Phoenix Incidents? or see Phoenix Incidents for Jira for Marketplace details.

What the app does in Slack

  • Incident reminders: acknowledge, verify, and post scheduled updates according to your SLAs.
  • Interactive controls: buttons and menus in messages to update incident state, severity, ownership, or status without leaving Slack*.
  • Channel workflow (optional): create or join incident channels to keep response focused.

Phoenix Incidents is Jira-first. Slack is used for notifications, interaction, and summaries — the source of record lives in Jira — right next your teams’ bugs and stories.

How it’s triggered & what it responds to

  • Slash command: /phoenix create to open a guided incident flow; /phoenix help for usage.
  • Interactive messages: actions from message buttons and menus update the incident in Jira.
  • From Jira: incident lifecycle events can trigger Slack* messages (e.g., created, state changes, required updates).

Interactivity is handled via our Slack Request URL endpoint; we do not subscribe to general message events.

Permissions we request

We request the minimum bot scopes required for posting messages, handling the /phoenix command, and (optionally) managing incident channels. Exact scopes are shown on Slack’s install screen.

  • commands — enable the /phoenix slash command (create, help).
  • chat:write — post incident messages, reminders, and updates.
  • users:read — map Slack users to incident roles and display names in messages.
  • channels:read / groups:read — discover channels/private channels the app can access to route notifications.
  • channels:join — allow the bot to join relevant channels for incident coordination.
  • channels:manage / groups:write — create dedicated Slack channels for each incident and auto-archive them when incidents close, keeping workspace hygiene manageable.

Least-privilege: channel management features are optional and can be disabled during rollout.

Interactivity & endpoints

  • Slash command URL: handled at our secured endpoint.
  • Interactivity (block actions): processed via our Request URL endpoint to update incidents and acknowledge actions.
  • Options requests: dynamic menu options are served via our Message Menu Options URL.

Installation & configuration

Install location: Phoenix Incidents for Slack is installed from the admin area inside Jira

  1. Open Apps in the Jira Administration area (underneath the ⛭ icon).
  2. Go to Phoenix Incidents → Messaging.
  3. Select Slack as your Chat Provider
  4. Click Connect Slack and approve scopes.

Data handling & security

  • Data stored: OAuth tokens, workspace/team IDs, and configuration (e.g., channel IDs, product mappings).
  • Message content: We post messages and process interactive payloads; we do not read arbitrary channel history.
  • Retention: Configuration and minimal metadata retained for operation; customers may request deletion at any time.

See our Privacy Policy and Security pages for details.

Uninstall

  • In Slack: App → Settings → Remove App.
  • Then remove the Slack connection in Phoenix Incidents for Jira to revoke tokens.

Support

* Microsoft Teams integration available in 2026.