IT OPS
Daily TLS Certificate Expiry Sweep with Owner Paging
Scans a list of HTTPS endpoints every morning, checks how many days until each TLS certificate expires.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires the sweep
- ActionProbe each endpoint and read cert notAfter dateShell
- LogicCompute days-to-expiry, classify healthy/warning/critical
- ActionOpen PagerDuty incident for critical certsPagerDuty
- OutputLog full sweep result to AxiomAxiom
What it does
Runs a scheduled sweep over your tracked HTTPS endpoints, reads each TLS certificate's expiry date, and computes days remaining. Certificates inside the danger window trigger a PagerDuty incident routed to the owning team, while everything healthy is logged silently. No more surprise outages from a cert that quietly lapsed over a weekend.
When to use it
Use this when you own more than a handful of public endpoints and renewals are not fully automated, or when automated renewal exists but you want an independent safety net that pages a human before a customer-facing outage.
How it works
- 1A daily schedule fires the sweep.
- 2A shell step probes each endpoint and extracts the certificate's notAfter date.
- 3A logic step computes days-to-expiry and splits endpoints into healthy, warning (under 30 days), and critical (under 7 days).
- 4Critical certs open a PagerDuty incident tagged with the endpoint and owner.
- 5A final output writes the full sweep result to Axiom for trend dashboards and audit history.
Set it up
What you configure once, before turning it on.
- 1Connect ShellRun sandboxed commands inside the workspace.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect AxiomLog streams, queries, dashboards.
- 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.