AI AGENTS

Escalation Runbook Handoff Executor

When an external alerting webhook signals an unresolved incident past its SLA, an agent walks the escalation runbook from Google Drive.

CategoryAI Agents
Enginepaperclip
Difficultyadvanced
Triggerwebhook
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerSLA-breach webhook receivedHTTP webhook
  • ActionFetch escalation runbook from Google DriveGoogle DriveGoogle Drive
  • LogicVerify breach and gate containment approval
  • ActionRun approved containment stepShell
  • ActionPage next tier with handoff briefPagerDutyPagerDuty
  • OutputPost escalation record to Slack threadSlack

What it does

Manages the escalation moment cleanly. When an inbound webhook reports an incident has breached its time-to-resolve SLA, the agent runs the escalation runbook: it performs the documented containment action on approval, then pages the next on-call tier with a complete handoff brief instead of a bare alert.

When to use it

Use it when incidents that stall need a structured handoff rather than a panicked re-page. It ensures the containment step is taken, the next responder gets context, and nothing is dropped between tiers.

How it works

  1. 1An inbound HTTP webhook fires when an incident breaches its SLA timer.
  2. 2The agent fetches the escalation runbook document from Google Drive.
  3. 3Logic checks the breach is genuine and not already acknowledged by the next tier.
  4. 4It requests approval in Slack for the documented containment action and runs it on yes.
  5. 5It assembles a handoff brief — timeline, steps taken, current state — and pages the next tier via PagerDuty.
  6. 6It posts the escalation record and brief link back to the Slack incident thread.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  2. 2
    Connect Google DriveDocs, sheets, slides, files.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Connect ShellRun sandboxed commands inside the workspace.
  5. 5
    Connect PagerDutyIncidents, on-call, escalations.
  6. 6
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  7. 7
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  8. 8
    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.