CHATBOTS

Confirm Degraded in Slack, Then Escalate to PagerDuty

When a user asks in Slack whether a service is degraded and Datadog confirms it is, the flow offers to escalate and, on confirmation, opens a PagerDuty incident for that service.

CategoryChatbots
Enginepaperclip
Difficultyadvanced
Triggerchat
Steps7
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerSlack message asks if a service is degradedSlack
  • ActionQuery Datadog monitor states for serviceDatadogDatadog
  • LogicHealthy: reply all-clear and stop
  • OutputReply degraded verdict + Escalate buttonSlack
  • LogicOn click, check for existing open incidentPagerDutyPagerDuty
  • ActionCreate PagerDuty incident for servicePagerDutyPagerDuty
  • OutputConfirm incident link in Slack threadSlack

What it does

Closes the loop between "is this broken?" and "someone go fix it." A teammate asks about a service in Slack; if Datadog confirms a degraded state and no incident already exists, the bot offers a one-click escalation that pages the right on-call rotation in PagerDuty.

When to use it

When non-on-call staff are often first to notice a problem but don't know how to page anyone. This lets them confirm the issue against live monitors and escalate responsibly, without false-paging on a healthy service.

How it works

  1. 1A Slack message or command asks whether a named service is degraded.
  2. 2The flow queries Datadog for that service's monitor states.
  3. 3A logic branch checks: if healthy, reply all-clear and stop.
  4. 4If degraded, the bot replies with the verdict and an "Escalate" action button.
  5. 5On click, a logic guard checks PagerDuty for an existing open incident to avoid duplicates.
  6. 6If none exists, it creates a PagerDuty incident tagged with the service and triggering monitor.
  7. 7The bot confirms the incident link back in the Slack thread.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SlackChannels, DMs, threads, mentions.
  2. 2
    Connect DatadogMetrics, traces, log search.
  3. 3
    Connect PagerDutyIncidents, on-call, escalations.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.