IT OPS
Domain Registration Expiry Escalation to PagerDuty
Watches domain registration (WHOIS) expiry dates for your portfolio and pages the on-call team through PagerDuty when a domain is within 45 days of expiring without auto-renew…
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule starts the domain check
- ActionRun WHOIS lookup per portfolio domainHTTP webhook
- LogicKeep domains within 45 days of expiry
- LogicMap days remaining to incident severity
- OutputOpen a PagerDuty incident for on-callPagerDuty
What it does
Monitors the registration expiry of every domain in your portfolio, not just the TLS cert. When a domain falls inside the 45-day window, it raises a PagerDuty incident severity-scaled by urgency so the registrar renewal happens before the domain drops and the brand goes dark.
When to use it
Use it when a lapsed domain registration would be catastrophic — losing the name itself, not just an SSL warning. Registrar auto-renew can fail silently on an expired card; this catches that gap and escalates to a human who can act.
How it works
- 1A daily schedule starts the check.
- 2A WHOIS lookup runs against each portfolio domain via an HTTP request to your WHOIS provider.
- 3A filter keeps domains under 45 days to expiry.
- 4A branch maps remaining days to PagerDuty severity: critical under 14 days, warning otherwise.
- 5PagerDuty opens an incident routed to the on-call domain owner with the registrar and expiry details.
- 6The result is logged so repeat runs dedupe against open incidents.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.