DEVOPS
Discord On-Call Shift Handoff Digest
At every shift change, assembles open incidents, deploys, and active alerts into a single Discord handoff message so the incoming engineer starts with full context.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule fires at shift boundary
- ActionFetch firing monitors from DatadogDatadog
- ActionPull merged PRs and releases from GitHubGitHub
- ActionRead open incidents from PostgresPostgres
- LogicAssemble and order handoff digest
- OutputPost digest to on-call Discord channelDiscord
What it does
Generates a structured shift-handoff digest and posts it to your on-call Discord channel at each rotation boundary. It pulls the currently firing alerts, the incidents opened during the outgoing shift, and the deploys that landed, then formats everything into one scannable message the incoming engineer can read in under a minute.
When to use it
Use it when your team runs follow-the-sun or daily on-call rotations and verbal or ad-hoc handoffs keep dropping context. It is ideal for teams whose monitoring lives in Datadog and whose deploy history lives in GitHub but who coordinate response in Discord.
How it works
- 1A schedule fires at each shift boundary (for example 09:00 and 21:00).
- 2The flow queries Datadog for monitors currently in alert or warn state.
- 3It pulls merged pull requests and releases from GitHub since the last handoff.
- 4It reads open-incident rows from the on-call Postgres table.
- 5A formatting step assembles a sectioned digest with severity ordering.
- 6The digest is posted to the on-call Discord channel, tagging the incoming role.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 4Connect DiscordCommunity channels + voice + bots.
- 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 DevOps workflows
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Auto-spin a Zoom war-room when PagerDuty hits SEV-1
When a PagerDuty incident escalates to a critical severity, this workflow creates a dedicated Zoom meeting and posts the bridge link to the incident's Slack channel so responders…
Page on-call when a Hugging Face Space build is stuck or errored
Polls Hugging Face Space runtime status on a schedule and opens a PagerDuty incident when a Space sits in a build or error state past a deadline, with a Slack heads-up.
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Open a Zoom war-room from a Datadog multi-alert storm
When a Datadog monitor crosses a critical threshold, this workflow dedupes against active incidents, and only for a genuinely new outage it creates a Zoom bridge.
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.