MARKETING

Pre-publish lab CWV gate: audit a preview URL, block bad deploys

On a new Vercel preview deployment, runs a headless lab audit of the landing page and, if LCP or CLS fails the budget, posts a blocking warning to Slack with the failing metrics…

CategoryMarketing
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerVercel preview deployment createdVercelVercel
  • ActionLoad preview URL headless and capture lab CWVBrowserbase
  • LogicCompare LCP/CLS/TBT to performance budget
  • LogicPass quietly if within budget
  • OutputPost blocking warning with metrics to SlackSlack

What it does

When Vercel creates a preview deployment for a landing page, this workflow loads the preview URL in a headless browser, measures lab Core Web Vitals (LCP, CLS, TBT), and checks them against a performance budget. If the preview fails, it posts a clear 'do not promote' warning to Slack with the failing metrics and the preview link so the change can be fixed before it reaches production RUM.

When to use it

Use it as a synthetic pre-publish gate that catches obvious performance regressions in lab conditions before real users ever hit the page — complementing field RUM monitoring with an upfront check.

How it works

  1. 1A Vercel preview-deployment webhook fires with the preview URL.
  2. 2A headless browser loads the page and captures lab CWV metrics.
  3. 3A branch compares each metric to the configured budget.
  4. 4If everything passes, the run ends with no noise.
  5. 5If any metric fails, the flow formats the failing values and budget.
  6. 6It posts a blocking warning with the preview link to Slack.

Set it up

What you configure once, before turning it on.

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