Public documentation for governed AI labor
SDKs/Governance/Connectors
Arx / Docs / Slack Escalation Bot

Documentation

Slack Escalation Bot

Project-Agent / library/workflows/slack-escalation-bot/README.md

Project-Agent repo-root library/workflows/slack-escalation-bot/README.md

Enables one-click escalation from Slack: when a team member reacts to an alert message with a specific emoji, the bot automatically creates a PagerDuty incident and a Jira tracking ticket.

Maturity: L3+ (Enforced and up)  ·  See the 5-level maturity model for where this workflow fits in your program.

Time Saved

~5 minutes per escalation of manual incident and ticket creation.

Connectors

| Connector | Operations | Risk Level | |-----------|-----------|------------| | Slack | reactions:read, conversations:history | Low — read-only | | PagerDuty | incidents:create | Low — creates incidents only | | Jira | issues:create | Low — creates tickets only |

How It Works

  1. Monitor Slack channels for the escalation emoji reaction (default: fire emoji).
  2. Fetch the original message that was reacted to.
  3. Extract alert context from the message text.
  4. Create a PagerDuty incident with the alert context.
  5. Create a Jira ticket linked to the PagerDuty incident.
  6. Reply in the Slack thread confirming escalation.

ARX Governance

Risk Classification

  • reactions:readLow. Read-only event monitoring.
  • conversations:historyLow. Read-only message retrieval.
  • incidents:create (PagerDuty) — Low. Creates on-call alerts.
  • issues:create (Jira) — Low. Creates tracking tickets.

HITL Gate Configuration

  • No HITL gate required. The emoji reaction itself serves as explicit human intent.

Policy Rules

  • reactions:readpermit — automated event monitoring.
  • conversations:historypermit — automated context retrieval.
  • incidents:createpermit — user-initiated via emoji reaction.
  • issues:createpermit — user-initiated via emoji reaction.

Audit Trail

  • Slack user who triggered the escalation, channel, and message timestamp.
  • PagerDuty incident ID and assigned responder.
  • Jira ticket key and linked PagerDuty reference.
  • Full event log written to arx.audit_log.

> See arx.yaml for the full governance configuration.

Setup Instructions

  1. Configure Slack, PagerDuty, and Jira connectors.
  2. Set environment variables:
  • SLACK_BOT_TOKEN, SLACK_MONITORED_CHANNELS
  • PAGERDUTY_API_KEY, PAGERDUTY_SERVICE_ID
  • JIRA_URL, JIRA_API_TOKEN, JIRA_PROJECT_KEY
  1. Configure the escalation emoji in arx.yaml (default: fire).
  2. Deploy with arx deploy slack-escalation-bot.

Schedule

Event-driven — triggered by Slack Events API (reaction_added).