IT OPS
End-of-Shift On-Call Handoff Brief to Slack
On a schedule at shift boundaries, pulls open PagerDuty incidents, recent Datadog alerts, and unresolved Sentry issues.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule fires at shift boundary
- ActionFetch open PagerDuty incidents + notesPagerDuty
- ActionPull Datadog alerts from shift windowDatadog
- ActionPull unresolved Sentry issues over thresholdSentry
- LogicGroup into Active / Watch / Resolved sections
- OutputPost handoff brief to on-call Slack channelSlack
What it does
Generates a complete shift-change handoff packet and posts it to your on-call Slack channel a few minutes before the rotation flips. The incoming engineer opens one message and sees everything that's still in flight: open incidents, who touched them last, alerts that fired during the shift, and Sentry issues still climbing.
When to use it
Use it when your team does scheduled rotations (daily or weekly) and verbal or ad-hoc handoffs keep dropping context. Best for teams already paging through PagerDuty with Datadog monitors and Sentry on the application layer.
How it works
- 1A schedule fires at the configured handoff time (e.g. 08:55 and 20:55).
- 2Fetch all triggered and acknowledged PagerDuty incidents plus their assignees and notes.
- 3Pull Datadog monitor alerts that transitioned in the last shift window.
- 4Pull unresolved Sentry issues above a frequency threshold.
- 5A formatting step groups everything into Active / Watch / Resolved-this-shift sections.
- 6Post the assembled brief as a single threaded Slack message tagging the next on-call.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect DatadogMetrics, traces, log search.
- 3Connect SentryErrors, performance, releases.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More IT Ops workflows
Daily Building Anomaly Digest to MS Teams
Each morning queries BigQuery for the prior day's flagged sensor anomalies, summarizes them by site and system into a ranked briefing.
Indoor Air Quality Breach to Tenant Notice and Work Order
Listens for CO2, VOC, or humidity sensor alerts via webhook, and when a zone exceeds occupant-safety limits it emails affected tenants, opens a Monday remediation task.
Self-Service Reclaim Email for Idle Users
Detects users idle in a SaaS app past the threshold and emails each one a keep-or-release link; unanswered seats after the deadline are auto-flagged for removal.
Outlook Room Conflict Resolver with Approval Gate in Teams
When an Outlook room clashes, proposes a rebooking and asks the bumped meeting's organizer to approve the move in Microsoft Teams before any change is made.
Outlook Room Double-Booking Resolver with Auto-Rebook
Detects when two meetings claim the same Outlook room resource and automatically relocates the lower-priority meeting to a comparable free room.
Monthly Wasted-License Cost Report
Aggregates inactive-seat data across all tracked SaaS apps each month, computes total reclaimable spend, and delivers a ranked cost report to leadership in Notion and Slack.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.