IT OPS

Daily Vercel Domain and Cert Inventory Snapshot to Axiom

Captures a daily structured snapshot of every Vercel domain, its assignment status, and certificate expiry into Axiom.

CategoryIT Ops
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule
  • ActionEnumerate domains and certs from VercelVercelVercel
  • LogicNormalize to flat event shape with days-to-expiry
  • ActionBatch-ship events to Axiom datasetAxiom
  • OutputConfirm ingested record count to SlackSlack

What it does

This workflow turns ephemeral Vercel API state into durable, queryable telemetry. Once a day it enumerates every domain across your projects, records assignment status, configuration health, and certificate `validFrom`/`validTo` dates, and ships one structured event per domain to Axiom. Over time this becomes the dataset your dashboards and threshold monitors query against.

When to use it

Use it as the data foundation under your domain monitoring. Point alerts at the Axiom dataset instead of re-scanning Vercel for every check, and answer questions like which domains churned this month or how cert lifetimes trend — things a point-in-time API call cannot tell you.

How it works

A daily schedule fires the run. An action pulls the complete domain list from Vercel and fetches certificate metadata for each. A logic step normalizes every domain into a flat event shape with consistent field names and computed days-to-expiry. An action batches and ships those events to an Axiom dataset. A final output confirms the ingested record count to Slack so a silent failure of the snapshot itself is visible.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect VercelDeploys, runtime logs, analytics.
  2. 2
    Connect AxiomLog streams, queries, dashboards.
  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.