IT OPS

Critical Cert Expiry Discord Escalation

Sweeps hosts on a short interval and, when any certificate falls under a hard critical threshold, posts a tagged Discord alert to the on-call channel for immediate action.

CategoryIT Ops
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerEvery-few-hours schedule triggers the scan
  • ActionShell: probe each host's cert expiryShell
  • LogicFilter to critical / already-expired certs
  • ActionPost tagged Discord alert to on-call channelDiscordDiscord
  • OutputEmit alert payload for auditDiscordDiscord

What it does

The same shell-based cert scan, but tuned for the danger zone. Instead of opening tickets, it watches for certificates within a critical window (e.g. 7 days or already expired) and pages the team in Discord with the hostname, exact expiry timestamp, and remaining hours.

When to use it

As the loud companion to your nightly Trello sweep. The board handles routine renewals; this flow exists to make sure a cert that slipped through gets a human's attention before it breaks production traffic.

How it works

  1. 1A frequent schedule (every few hours) triggers the scan.
  2. 2A shell step probes each host with openssl and returns days-to-expiry.
  3. 3A logic step filters to certs at or below the critical threshold, including any already expired.
  4. 4If the filtered set is non-empty, a Discord action posts to the on-call channel with an `@here` mention and a per-host breakdown.
  5. 5The flow outputs the alert payload so the run is auditable.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ShellRun sandboxed commands inside the workspace.
  2. 2
    Connect DiscordCommunity channels + voice + bots.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    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.