DEVOPS

Nightly canary sweep across all open preview deploys

On a nightly schedule, enumerates every active Vercel preview deployment, runs a quick health-and-critical-path sweep on each.

CategoryDevOps
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNightly schedule fires
  • ActionList all active Vercel preview deploymentsVercelVercel
  • ActionRun health and critical-path check on each previewBrowserbase
  • LogicRank previews by status, broken first
  • OutputPost ranked digest to SlackSlack
  • OutputArchive dated digest to NotionNotionNotion

What it does

This workflow runs a nightly sweep across every open preview. It lists all active Vercel preview deployments, hits each one's health and critical paths in a browser, and rolls everything into one ranked digest so the team starts the day knowing which feature branches have rotted.

When to use it

Use it on teams with many long-lived feature branches where stale previews silently break and nobody notices until they try to demo or merge.

How it works

  1. 1A nightly schedule fires the workflow.
  2. 2The Vercel API returns all active preview deployments with their URLs and branches.
  3. 3Browserbase runs a quick health-and-critical-path check on each preview in turn.
  4. 4A logic step ranks previews by status, surfacing broken ones first with the failing path noted.
  5. 5The digest is posted to Slack for the team.
  6. 6The same ranked digest is archived to a Notion page to keep a dated history of preview health.

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
    Connect NotionPages, databases, comments.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.