ENGINEERING

Scheduled staleness sweep of open-PR Vercel previews

On a daily schedule, re-smoke-tests the live preview for every open pull request and posts a single digest to Slack listing which previews are now broken or stale so reviewers…

CategoryEngineering
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule
  • ActionList open PRs and latest previewsGitHubGitHub
  • ActionResolve preview URLs from VercelVercelVercel
  • ActionSmoke-test each preview over HTTPHTTP webhook
  • LogicBucket as healthy, broken, or stale
  • OutputPost consolidated digest to SlackSlack

What it does

Once a day this workflow lists every open pull request with a Vercel preview, re-runs a smoke check against each preview URL, and posts one consolidated Slack digest ranking previews as healthy, broken, or stale — so reviewers never waste time on a preview that died since it was built.

When to use it

Use it on busy repos where PRs sit open for days and their previews silently rot (backend changed, env expired, deploy reaped). A daily sweep keeps the review queue honest.

How it works

  1. 1A daily schedule trigger starts the sweep.
  2. 2The flow lists open PRs and their latest preview deployments from GitHub and Vercel.
  3. 3An HTTP smoke request runs against each preview URL.
  4. 4A logic step buckets each into healthy, broken, or stale based on status and deploy age.
  5. 5A single Slack digest posts the buckets with direct links so the team can re-trigger or close as needed.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitHubRepos, issues, pull requests, actions.
  2. 2
    Connect VercelDeploys, runtime logs, analytics.
  3. 3
    Connect HTTP webhookTrigger any URL on agent actions.
  4. 4
    Connect SlackChannels, DMs, threads, mentions.
  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.