IT OPS
Cloudflare Decommission DNS Reconciler
Webhook-triggered reconciliation that, when an origin is marked decommissioned, finds every Cloudflare record pointing at it, opens a GitLab issue per record.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook fires with the decommissioned originHTTP webhook
- ActionPull and match Cloudflare records against the originCloudflare
- LogicKeep only records targeting the retired host
- ActionOpen a GitLab cleanup issue per matching recordGitLab
- OutputNotify the owning team in SlackSlack
What it does
When a host or service is decommissioned, the DNS pointing at it usually outlives it. This workflow listens for a decommission event, then immediately finds every Cloudflare record whose target resolves to the retired origin and turns each into a tracked cleanup task. It closes the loop between "we killed the server" and "we cleaned up its DNS."
When to use it
Wire it into your decommission runbook or infrastructure tooling so retiring an origin automatically kicks off DNS cleanup. It prevents the dangling records that webhook-driven teardown otherwise leaves behind.
How it works
- 1A webhook fires with the decommissioned origin's hostname or IP.
- 2Cloudflare records across all zones are pulled and matched against that origin.
- 3A filter keeps only records that actually target the retired host.
- 4A GitLab issue is opened per matching record, labeled `decommission-cleanup`, assigned to the record's owning group.
- 5A Slack message notifies the owning channel with the list of records and their tickets.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 3Connect GitLabRepos, MRs, pipelines, registry.
- 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.