IT OPS

Daily Cloudflare Cert-Expiry Sweep with Owner-Routed ClickUp Tasks

Scans every certificate across all your Cloudflare zones once a day, and for any cert expiring inside the warning window it opens a ClickUp renewal task assigned to the zone's…

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule fires the sweep
  • ActionList zones and fetch each zone's certsCloudflareCloudflare
  • LogicKeep only certs inside the warning window
  • LogicResolve zone owner and dedupe against open tasksClickUpClickUp
  • OutputCreate owner-assigned ClickUp renewal taskClickUpClickUp

What it does

Every morning this workflow pulls the full certificate list from each Cloudflare zone you manage, calculates days-to-expiry for each one, and creates a tracked renewal task in ClickUp for anything inside your warning threshold (default 30 days). Each task is routed to the engineer who owns that zone, so renewals never fall through the cracks.

When to use it

Run this when you operate more than a handful of Cloudflare zones and manual cert tracking has become error-prone. It is the safety net that catches edge certificates, origin certs, and custom hostnames before they lapse and break production traffic.

How it works

  1. 1A daily schedule fires the sweep at a fixed hour.
  2. 2The workflow lists all zones, then fetches each zone's certificate inventory from Cloudflare.
  3. 3A filter keeps only certs whose expiry falls within the warning window.
  4. 4For each surviving cert it looks up the zone owner from a mapping and checks ClickUp for an existing open renewal task.
  5. 5If none exists, it creates a ClickUp task with the hostname, expiry date, and due date, assigned to the owner.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
  2. 2
    Connect ClickUpDocs + tasks + chats in one workspace.
  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.