IT OPS

On-Demand Handoff Packet via Slack Slash Command

When an engineer triggers a Slack slash command, instantly assembles current open incidents, active alerts, and watch-items into a handoff packet and replies in-thread.

CategoryIT Ops
Enginesim
Difficultybeginner
Triggerwebhook
Steps6
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerSlack slash command webhookSlack
  • ActionFetch open/acknowledged PagerDuty incidentsPagerDutyPagerDuty
  • ActionFetch Datadog monitors in alert/warnDatadogDatadog
  • ActionFetch unresolved Sentry issues over thresholdSentrySentry
  • LogicAssemble live packet with timestamps + owners
  • OutputReply with packet in Slack threadSlack

What it does

Generates the same handoff packet as the scheduled version, but on demand. An engineer who needs to hand off early — stepping away, going off-shift unexpectedly, escalating to a teammate — runs a Slack slash command and gets a live snapshot of open PagerDuty incidents, firing Datadog alerts, and active Sentry issues posted right back into the channel.

When to use it

Use it for ad-hoc and unplanned handoffs that don't line up with the rotation schedule, or any time someone wants a fresh on-the-spot view of the current operational state without digging through three dashboards.

How it works

  1. 1A Slack slash command (e.g. /handoff) triggers via webhook with the requesting user.
  2. 2Fetch all open and acknowledged PagerDuty incidents.
  3. 3Fetch Datadog monitors currently in an alert or warn state.
  4. 4Fetch unresolved Sentry issues over the noise threshold.
  5. 5A formatting step assembles the live packet with timestamps and ownership.
  6. 6Reply with the packet in the originating Slack thread for the whole channel to see.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SlackChannels, DMs, threads, mentions.
  2. 2
    Connect PagerDutyIncidents, on-call, escalations.
  3. 3
    Connect DatadogMetrics, traces, log search.
  4. 4
    Connect SentryErrors, performance, releases.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.