IT OPS

Expiring Cert Triage Agent with Owner Routing to Linear

An agent runs weekly, gathers all certs and domains nearing expiry, reasons about which team owns each asset.

CategoryIT Ops
Enginepaperclip
Difficultyadvanced
Triggerschedule
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule starts the triage agent
  • ActionPull cert and zone inventory with datesCloudflareCloudflare
  • LogicAgent classifies asset type and owner
  • ActionFile a routed Linear issue per assetLinearLinear
  • OutputPost routing digest to SlackSlack

What it does

Instead of a fixed rule, an agent reviews the week's upcoming cert and domain expiries, infers the owning team from asset naming and the service catalog, and writes a tailored Linear issue per asset — a wildcard cert, an apex domain, and an internal mTLS cert each get different drafted renewal steps and the correct assignee.

When to use it

Use it when your estate is large and heterogeneous enough that a single ClickUp template doesn't fit, and tickets keep landing on the wrong team. The agent does the triage a senior operator would do by hand.

How it works

  1. 1A weekly schedule starts the triage agent.
  2. 2Cloudflare supplies the certificate and zone inventory with expiry dates.
  3. 3The agent filters to assets expiring within 60 days and classifies each by type and likely owner using naming and catalog context.
  4. 4For each, it drafts asset-specific renewal steps and an assignee.
  5. 5Linear receives one routed issue per asset with the drafted plan.
  6. 6A Slack digest lists every issue created and to whom it was routed.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
  2. 2
    Connect LinearIssues, projects, cycles, triage.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.