DEVOPS
Hold Vercel preview promotion on unreviewed visual diffs
Captures screenshots of key pages on each Vercel preview, diffs them against the production baseline.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel preview deployment readyVercel
- ActionScreenshot key pages on previewBrowserbase
- LogicVisual diff exceeds threshold?
- ActionRequest approval in SlackSlack
- OutputPromote deployment on approvalVercel
What it does
This workflow catches unintended UI changes before they ship. For each preview, it screenshots a set of key pages, compares them pixel-by-pixel against the current production baseline, and measures the change. Small diffs auto-approve and promote. Diffs above your threshold are paused: the workflow posts the before/after images to Slack with approve and reject buttons, and promotion only proceeds on human approval.
When to use it
Use it when visual regressions are a real risk and you want a human in the loop only when the UI actually changed. It keeps routine deploys fast while forcing review of meaningful layout or styling shifts.
How it works
- 1Vercel fires a deployment.ready webhook for a preview build.
- 2A headless browser captures screenshots of the configured key pages.
- 3The flow diffs each screenshot against the stored production baseline.
- 4A branch checks whether any diff exceeds the change threshold.
- 5If exceeded, it posts the visual diffs to Slack for approve/reject and gates promotion on the response.
- 6On approval or a sub-threshold diff, it promotes the deployment via the Vercel API.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect BrowserbaseHeadless browsers, sessions, replays.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Open a Zoom war-room from a Datadog multi-alert storm
When a Datadog monitor crosses a critical threshold, this workflow dedupes against active incidents, and only for a genuinely new outage it creates a Zoom bridge.
Auto-spin a Zoom war-room when PagerDuty hits SEV-1
When a PagerDuty incident escalates to a critical severity, this workflow creates a dedicated Zoom meeting and posts the bridge link to the incident's Slack channel so responders…
Spin up a war-room on demand from a Slack slash command
When an engineer runs a Slack command, this workflow creates a Zoom bridge, opens a tracking Sentry-linked incident, files a Linear issue for follow-up.
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.