DEVOPS
Agent-Driven Cross-System On-Call Handoff
An agent assembles a richer shift-handoff by reasoning across PagerDuty incidents, Sentry error spikes, and open GitHub PRs.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule fires at shift change
- ActionQuery PagerDuty active and recent incidentsPagerDuty
- ActionPull overnight Sentry error groupsSentry
- ActionCheck GitHub for risky merged/open PRsGitHub
- LogicAgent correlates and ranks risks
- ActionWrite handoff doc in NotionNotion
- OutputDM risk headline to incoming on-call in SlackSlack
What it does
Instead of a fixed template, an agent investigates the overnight state across three systems — open and recent PagerDuty incidents, new or escalating Sentry issues, and risky in-flight GitHub deploys or PRs — and reasons about what the incoming on-call engineer most needs to watch. It writes a full handoff doc in Notion and sends a terse risk headline to Slack.
When to use it
Use it when handoffs need judgment, not just a list: correlating a Sentry spike to a merged PR, or flagging that an open incident touches a service with a deploy mid-flight. Good for senior rotations where context-stitching matters.
How it works
- 1A schedule fires at shift change.
- 2The agent queries PagerDuty for active and recent incidents.
- 3It pulls Sentry for new and escalating error groups overnight.
- 4It checks GitHub for recently merged or open PRs touching affected services.
- 5The agent correlates findings, judges what is risky, and writes a Notion handoff doc.
- 6It posts a one-line risk summary to the incoming engineer in Slack.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect SentryErrors, performance, releases.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 4Connect NotionPages, databases, comments.
- 5Connect SlackChannels, DMs, threads, mentions.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
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.
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.
Generate a weekly de-flake report and assign Linear cleanup tickets
On a weekly schedule, aggregates the current quarantine manifest and recent flake history, builds a prioritized report.
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-release tests from quarantine once they prove stable
Triggered by a webhook from a nightly stability runner, checks whether quarantined tests have passed enough consecutive runs, removes the stable ones from quarantine in GitHub.
Quarantine a test on demand from a PR comment command
Triggered when an engineer comments a quarantine command on a pull request, validates the test name, commits the quarantine change to that PR branch, opens a tracking issue.
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.