IT OPS
Tiered Certificate Expiry Escalation: Slack Nudge then Page
Checks certificate expiry daily and escalates progressively — a gentle Slack reminder at 30 days, a louder channel ping at 14 days, and a PagerDuty page at 3 days.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule starts the run
- ActionCollect cert expiry dates for all endpointsShell
- LogicBucket certs into 30 / 14 / 3-day tiers
- ActionPost reminders for 30 and 14-day tiers to SlackSlack
- ActionPage on-call via PagerDuty for 3-day tierPagerDuty
- OutputRecord tier decisions to AxiomAxiom
What it does
Applies graduated urgency to expiring certificates instead of a single all-or-nothing alert. Far-out certs get a low-noise Slack nudge to the owning team, mid-range certs get a more prominent warning, and only certs about to lapse trigger a PagerDuty page. This matches alert loudness to actual risk and prevents alert fatigue.
When to use it
Use this when a flat threshold either pages too early (annoying) or too late (risky). The tiered model gives teams runway to renew calmly while guaranteeing a human is paged if a cert reaches the danger zone.
How it works
- 1A daily schedule starts the run.
- 2A shell step collects each endpoint's certificate expiry date.
- 3A logic step buckets every cert by days remaining into the 30, 14, and 3-day tiers.
- 430 and 14-day buckets post a formatted reminder to the owning team's Slack channel.
- 5The 3-day bucket opens a PagerDuty incident as a hard escalation.
- 6A closing output records each tier decision to Axiom for reporting.
Set it up
What you configure once, before turning it on.
- 1Connect ShellRun sandboxed commands inside the workspace.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 4Connect AxiomLog streams, queries, dashboards.
- 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.