IT OPS

Critical Cloudflare Cert Expiry to PagerDuty Incident

Watches Cloudflare certificates several times a day and, for any production-zone cert inside the critical window or already expired.

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerFrequent schedule fires for tight coverage
  • ActionRead cert expiry for production-tagged zonesCloudflareCloudflare
  • LogicKeep only critical-window or expired certs
  • LogicBuild stable dedup key per certificate
  • OutputOpen or update routed PagerDuty incidentPagerDutyPagerDuty

What it does

This workflow treats an imminent cert lapse on a production zone as a pageable incident. It checks Cloudflare certificates on a frequent cadence, and when a production cert falls inside the critical window or has already expired it opens a PagerDuty incident with a dedup key so the same cert never pages twice. Lower-priority zones are intentionally excluded.

When to use it

Use it for the small set of domains where an expired certificate is a customer-facing outage. This is the last line of defense behind your task-based sweeps — if everything else was missed, the on-call gets paged before traffic breaks.

How it works

  1. 1A schedule fires several times a day for tight coverage.
  2. 2The workflow reads certificate expiry for the zones tagged production.
  3. 3A filter keeps only certs inside the critical window or already expired.
  4. 4It builds a stable dedup key per certificate to prevent duplicate pages across runs.
  5. 5It opens or updates a PagerDuty incident with the hostname, expiry, and severity, routing to the correct escalation policy.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
  2. 2
    Connect PagerDutyIncidents, on-call, escalations.
  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.