IT OPS

TLS Certificate Expiry Watchdog with ClickUp Renewal Tasks

Checks every TLS certificate in your Cloudflare account daily and opens a ClickUp renewal task whenever one is within 30 days of expiring, so certs never lapse silently.

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule fires the expiry sweep
  • ActionList all TLS certificates and expiry datesCloudflareCloudflare
  • LogicKeep certs within 30 days of expiry
  • LogicSet priority: Urgent under 7 days, else High
  • ActionOpen a ClickUp renewal task per certClickUpClickUp
  • OutputPost a run summary to SlackSlack

What it does

Runs a daily sweep of all certificates Cloudflare manages for your zones, measures days-to-expiry for each, and creates a prioritized ClickUp task for any cert crossing the 30-day threshold. The task carries the hostname, issuer, exact expiry date, and remaining days so an operator can renew before the outage window.

When to use it

Use it when you run more than a handful of domains behind Cloudflare and a single expired edge cert would break production. It replaces the spreadsheet someone updates by hand and the inevitable 2am page when a renewal slips.

How it works

  1. 1A daily schedule fires the run at a fixed early-morning hour.
  2. 2Cloudflare returns the certificate inventory across all configured zones with their expiry timestamps.
  3. 3A filter computes days remaining and keeps only certs at or under 30 days.
  4. 4A branch sets task priority: Urgent under 7 days, High otherwise.
  5. 5ClickUp creates one renewal task per matching cert with full metadata and a due date set to seven days before expiry.
  6. 6A Slack message summarizes how many tasks were opened this run.

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
    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.