MARKETING

Block a Vercel production promotion when LCP or CLS regress

When a Vercel preview deployment is ready, runs a lab Core Web Vitals check on key landing routes and promotes to production only if LCP and CLS stay within budget.

CategoryMarketing
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerVercel preview deployment readyVercelVercel
  • ActionRun lab CWV audit on key routesBrowserbase
  • LogicCompare LCP/CLS to budget
  • ActionPromote preview to production aliasVercelVercel
  • OutputPost hold + failing metrics to SlackSlack

What it does

Gates the promotion of a Vercel preview to production behind a Core Web Vitals budget. It measures LCP and CLS on a fixed set of revenue landing routes and refuses to promote a build that degrades them, so a slow hero image or a layout-shifting banner never reaches the live marketing site.

When to use it

Use it on marketing or growth teams that ship landing pages frequently and have been burned by silent performance regressions. It fits any repo deployed through Vercel where the production alias is promoted from a preview.

How it works

  1. 1A Vercel deployment-ready webhook fires for a new preview build.
  2. 2The flow runs a synthetic Lighthouse-style audit against the preview URL for each tracked route and reads back LCP and CLS.
  3. 3A logic step compares each metric to the budget (e.g. LCP under 2.5s, CLS under 0.1).
  4. 4If every route passes, it calls the Vercel API to promote the preview to the production alias.
  5. 5If any route fails, it skips promotion and posts the failing routes and numbers to Slack for a human decision.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect VercelDeploys, runtime logs, analytics.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Connect BrowserbaseHeadless browsers, sessions, replays.
  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.