IT OPS

On-Demand Cloudflare Cert Audit via Webhook to Notion Tracker

Exposes a webhook that audits one Cloudflare zone's certificates on request and writes a full inventory row per cert into a Notion tracker.

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerInbound webhook with zone identifierHTTP webhook
  • LogicValidate payload and confirm zone exists
  • ActionFetch all certs and compute per-cert statusCloudflareCloudflare
  • ActionUpsert one row per cert into Notion trackerNotionNotion
  • OutputReturn valid/expiring/expired summary to callerHTTP webhook

What it does

This is the on-demand counterpart to the scheduled sweep. You hit a webhook with a zone identifier and it returns and records a complete certificate inventory for that zone in Notion — issuer, hosts covered, validity dates, and a computed status (valid, expiring, expired). It is built for the moment you add a zone and want a clean baseline rather than waiting for the next nightly run.

When to use it

Reach for it during zone onboarding, after a migration, or whenever someone asks "are we covered on that domain?" and you need an answer now plus a durable record.

How it works

  1. 1An inbound webhook call carries the target zone identifier.
  2. 2The workflow validates the payload and confirms the zone exists.
  3. 3It pulls every certificate for that zone from Cloudflare and computes per-cert status against today's date.
  4. 4For each cert it upserts a row into the Notion certificate tracker database, updating any existing entry for the same host.
  5. 5It returns a summary count of valid, expiring, and expired certs to the webhook caller.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  2. 2
    Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
  3. 3
    Connect NotionPages, databases, comments.
  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.