IT OPS
Critical DNS Record Drift to PagerDuty Incident
Frequently checks a small allowlist of business-critical DNS records against the manifest and, if a protected record is changed or deleted, opens a PagerDuty incident…
How it runs
The automated pipeline, trigger to output.
- TriggerShort-interval schedule fires
- ActionFetch watched critical records from CloudflareCloudflare
- ActionRead expected values from GitHub manifestGitHub
- LogicCompare protected records; exit if all match
- ActionOpen PagerDuty incident for drifted recordPagerDuty
- OutputFile GitHub issue for trackingGitHub
What it does
This workflow watches only the DNS records you cannot afford to lose, such as apex A records, mail MX, and SPF/DKIM TXT records. It checks them often against the manifest and, on any unauthorized change, escalates immediately as a paging incident rather than a passive report.
When to use it
Use it for high-blast-radius records where drift means an outage or a deliverability failure. The hourly audit covers everything quietly; this one is the tripwire that wakes someone up. The narrow allowlist keeps it noise-free so a page always means something genuinely critical moved.
How it works
- 1A short-interval schedule triggers the critical-record check.
- 2The flow fetches the watched records from Cloudflare by name and type.
- 3It reads the expected values for those same records from the GitHub manifest.
- 4A logic step compares them and exits if every protected record matches.
- 5On a mismatch, an action opens a PagerDuty incident with the drifted record and its expected value.
- 6A final action files a GitHub issue capturing the drift for tracking and postmortem.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.