IT OPS
Critical Cert Expiry Dual Escalation to PagerDuty and Teams
When a certificate crosses the 7-day critical threshold it pages on-call via PagerDuty and simultaneously posts an actionable card to the responsible team's Microsoft Teams…
How it runs
The automated pipeline, trigger to output.
- TriggerFrequent schedule for critical-window coverage
- ActionPull current certificates from CloudflareCloudflare
- LogicFilter to certs at or under 7 days to expiry
- ActionPage on-call via PagerDuty incidentPagerDuty
- OutputPost actionable renewal card to owning team in TeamsMicrosoft Teams
What it does
Watches for certificates entering the final critical window and escalates on two tracks at once: an immediate PagerDuty page to whoever is on-call, and a rich Microsoft Teams card to the service-owning team with the cert details and a renewal checklist. This closes the gap where on-call gets paged but the team that actually owns the service never finds out.
When to use it
When ownership and on-call are separate — a central SRE rotation responds to pages but a product team owns the renewal. Use it for the tightest expiry window where you want redundant, parallel escalation rather than a single channel.
How it works
- 1A schedule runs the critical sweep multiple times a day for tight coverage.
- 2The flow pulls current certs from Cloudflare and computes days remaining.
- 3A filter keeps only certificates at or under 7 days to expiry.
- 4For each critical cert it triggers a PagerDuty incident routed to the on-call service.
- 5In parallel it posts an actionable Teams card to the owning team's channel with hostname, expiry, owner, and a renewal checklist.
- 6Both escalations reference the same incident ID so responders and owners stay in sync.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect Microsoft TeamsChannels, chats, files.
- 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.