IT OPS

Tiered Cloudflare Cert Expiry Slack Escalation

Checks Cloudflare certificate expiry daily and posts to Slack with a severity that escalates as the deadline nears: a quiet heads-up at 30 days, an owner @-mention at 14.

CategoryIT Ops
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule starts the check
  • ActionRead cert expiry for all Cloudflare zonesCloudflareCloudflare
  • LogicBucket each cert into a 30/14/3-day tier
  • LogicDrop certs outside every warning tier
  • OutputPost tier-matched Slack alert with @-mentionSlack

What it does

This workflow turns cert expiry into a graduated Slack signal instead of a single noisy alert. As each Cloudflare certificate approaches its expiry date it raises the urgency of the message: an informational note far out, a direct owner ping in the middle, and a loud channel-wide warning when the cert is about to lapse.

When to use it

Use it when a flat daily digest gets ignored and you want urgency to scale with risk. Good for teams that live in Slack and need the message tone to match how close a certificate is to breaking traffic.

How it works

  1. 1A daily schedule starts the check.
  2. 2The workflow reads certificate expiry data for every Cloudflare zone.
  3. 3A branch buckets each cert into a tier by days remaining: 30, 14, or 3 and under.
  4. 4Certs outside all tiers are dropped so the channel stays quiet on healthy days.
  5. 5Each tier maps to a Slack message style — plain note, owner @-mention, or @here channel alert — and the workflow posts the matching message with hostname and expiry date.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  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.