IT OPS
Certificate Renewal Owner Investigator and Dispatcher
For each near-expiry certificate, an agent figures out the responsible service owner from your records, drafts a renewal action plan, files a tracking ticket.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule starts investigation pass
- ActionPull certs entering renewal window from AxiomAxiom
- ActionAgent identifies owner and drafts renewal plan
- LogicBranch on whether an owner was confidently found
- ActionFile Linear ticket for known ownersLinear
- ActionPage PagerDuty for unidentified ownersPagerDuty
- OutputPost dispatched-renewals digest to SlackSlack
What it does
Goes beyond detection to accountability. When a certificate approaches expiry, an agent investigates who owns the service behind it, assembles the renewal steps and links, and opens a tracked ticket assigned to that owner. If ownership is ambiguous or missing, it escalates to PagerDuty so the cert is never silently orphaned.
When to use it
Use this in larger estates where the hard part is not detecting expiry but routing it to the right human with enough context to act. It turns a raw alert into an assigned, documented renewal task.
How it works
- 1A daily schedule starts the investigation pass.
- 2An Axiom action pulls certificates entering the renewal window.
- 3An agent step reasons over service metadata to identify the owning team and drafts a renewal plan.
- 4A logic step branches on whether an owner was confidently found.
- 5Found owners get a Linear ticket created with the plan and deadline; unknown owners trigger a PagerDuty page.
- 6A final output posts a digest of dispatched renewals to Slack.
Set it up
What you configure once, before turning it on.
- 1Connect AxiomLog streams, queries, dashboards.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 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
Recurring Sensor Fault Root-Cause Investigator
On a schedule, an agent reviews recent Monday work orders and BigQuery telemetry to identify equipment with repeating faults, drafts a root-cause hypothesis with a recommended fix.
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.
Agentic Inactive-Seat Reclamation Review
An agent investigates each idle SaaS seat by correlating SSO login gaps with HR status and ticket history, classifies it as reclaim, hold, or escalate, and drafts a reasoned…
Reconcile SSO logins against expense spend to find unmanaged tools
Joins SSO usage data with expense/payment records in Snowflake to surface tools that are being used but not paid for, or paid for but never logged.
Approved-Seat Deprovision Execution
Fires when an IT approver confirms a seat for removal, then executes deprovisioning via the IdP API and logs the action to an audit table and a Linear cleanup ticket.
HVAC Anomaly Detection to Severity-Routed Work Orders
Ingests building HVAC telemetry via webhook, flags out-of-band temperature, pressure, or runtime readings.
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.