IT OPS

Pre-Renewal CAA and DNS Readiness Check for Vercel Certs

Ahead of each certificate's renewal window, verifies that Cloudflare CAA records and DNS targets permit Vercel to issue a new cert.

CategoryIT Ops
Enginesim
Difficultyadvanced
Triggerschedule
Steps7
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule
  • ActionList Vercel domains with cert expiry datesVercelVercel
  • LogicNarrow to certs renewing within 30 days
  • ActionRead CAA and validation records from CloudflareCloudflareCloudflare
  • LogicEvaluate issuance prerequisites
  • ActionFile Linear ticket for failing domainsLinearLinear
  • OutputPost weekly readiness digest to SlackSlack

What it does

This workflow prevents failed renewals before they happen. For every Vercel domain whose cert renews soon, it checks the prerequisites in Cloudflare that issuance depends on — that CAA records allow Vercel's issuing CA, that the validation CNAME or A records resolve correctly, and that the zone is reachable. Domains that would fail get a tracked ticket, not a 2 a.m. page.

When to use it

Use it when you want renewal problems handled as planned work during business hours instead of as incidents. It shifts cert hygiene left, turning a future outage into a routine ticket an engineer clears on their own time.

How it works

A weekly schedule starts the run. An action lists Vercel domains and their cert expiry dates, and a logic step narrows to those renewing within 30 days. For each, an action reads the relevant CAA and validation records from Cloudflare and a logic step evaluates whether issuance prerequisites are satisfied. Any domain that fails the check produces a Linear issue via an action, labeled and assigned to the platform team with the exact missing or wrong record. An output posts a weekly readiness digest to Slack.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect VercelDeploys, runtime logs, analytics.
  2. 2
    Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
  3. 3
    Connect LinearIssues, projects, cycles, triage.
  4. 4
    Connect SlackChannels, DMs, threads, mentions.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.