ENGINEERING
Vercel preview visual regression gate with PagerDuty escalation
Screenshots key pages on a Vercel preview, compares them against the Figma design baseline.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel preview deployment readyVercel
- ActionScreenshot configured pages on previewBrowserbase
- ActionPull baseline frames from FigmaFigma
- LogicBranch on visual drift threshold
- ActionOpen PagerDuty incident on major driftPagerDuty
- OutputPost diff images to Slack for triageSlack
What it does
When a Vercel preview deploys, this workflow captures screenshots of designated pages, compares them to the approved Figma frames, and quantifies visual drift. If drift crosses your threshold it escalates: a PagerDuty incident for the on-call front-end engineer and a Slack alert with side-by-side diff images.
When to use it
Use it when unintended UI regressions are a recurring pain and you want preview deploys to catch layout or styling drift against the source-of-truth designs before review, with real escalation when something breaks badly.
How it works
- 1A Vercel preview-ready webhook provides the preview URL.
- 2A browser session screenshots each configured page on the preview.
- 3The workflow pulls the matching baseline frames from Figma and computes a per-page diff score.
- 4A logic step branches on the threshold: minor drift is logged, major drift escalates.
- 5On major drift it opens a PagerDuty incident and posts the diff images to Slack for triage.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect BrowserbaseHeadless browsers, sessions, replays.
- 3Connect FigmaFiles, frames, comments, assets.
- 4Connect PagerDutyIncidents, on-call, escalations.
- 5Connect SlackChannels, DMs, threads, mentions.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Engineering workflows
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Block PRs that add incompatible Hugging Face model licenses
When a pull request adds or bumps a Hugging Face model dependency, it fetches the model card license, checks it against your org's allowed-license policy.
Quarterly Logging Hygiene Audit Agent
An agent-driven quarterly sweep that surveys all Axiom datasets, builds a logging-hygiene scorecard per service.
Post-Merge Log Volume Recheck After Downsampling PR
After a log-level PR merges, waits a day then re-queries Axiom to confirm the targeted stream's volume actually dropped.
Axiom Ingest Cost Spike to Linear Triage Ticket
When Axiom ingest volume spikes beyond its baseline, identifies which service caused it and files a Linear ticket with the offending log stream, sample lines, and a downsampling…
File a Linear license-review ticket for risky model adds
When a PR introduces a Hugging Face model with a non-permissive or unknown license, it opens a Linear issue assigned to the legal-review team with the model, license.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.