IT OPS
Weekly Handoff Archive and Rollup to Google Drive
On a weekly schedule, consolidates the week's resolved incidents, recurring alerts, and lingering watch-items from PagerDuty, Datadog, and Sentry into a single rollup document…
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionPull week's resolved PagerDuty incidentsPagerDuty
- ActionTally repeat-firing Datadog monitorsDatadog
- ActionPull week-long unresolved Sentry issuesSentry
- LogicRank recurring offenders + compute load stats
- OutputSave dated rollup doc to Google DriveGoogle Drive
What it does
Rolls a week of operational activity into one archived handoff document. It pulls every resolved PagerDuty incident, identifies which Datadog monitors fired repeatedly (the chronic noise), and lists Sentry issues that stayed unresolved all week, then writes a dated rollup file to a Google Drive folder. This is the long-memory companion to the per-shift briefs.
When to use it
Use it to feed weekly retros, spot recurring pain that single shifts miss, and keep an audit trail of operational load over time. Ideal for engineering managers and reliability leads, not just the person on call.
How it works
- 1A weekly schedule fires (e.g. Monday morning).
- 2Pull all PagerDuty incidents resolved in the past seven days with durations.
- 3Pull Datadog alert history and tally which monitors fired most often.
- 4Pull Sentry issues that remained unresolved across the week.
- 5A logic step ranks recurring offenders and computes weekly load stats.
- 6Generate a dated rollup document and save it to the Google Drive retro folder.
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 Google DriveDocs, sheets, slides, files.
- 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.