ENGINEERING

Vercel preview smoke gate with Slack review card

When a Vercel preview deploy succeeds, runs an HTTP smoke check against the preview URL and posts a pass/fail review card to Slack with the deploy link, status code, and latency.

CategoryEngineering
Enginesim
Difficultybeginner
Triggerwebhook
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerVercel preview deployment readyVercelVercel
  • LogicFilter to preview deploys only
  • ActionHTTP smoke request to preview URLHTTP webhook
  • LogicDecide pass or fail on status + latency
  • OutputPost pass/fail review card to SlackSlack

What it does

Every time a Vercel preview deployment reaches the ready state, this workflow hits the preview URL with a smoke request, evaluates the response, and posts a color-coded review card to your engineering Slack channel so reviewers see a clear pass or fail before they open the PR.

When to use it

Use it when your team relies on Vercel preview deploys for PR review and you want a fast automated sanity check — is the preview actually up and serving 200s — without anyone manually clicking the link first.

How it works

  1. 1A Vercel deployment-ready webhook fires with the preview URL and metadata.
  2. 2The flow filters to preview (not production) deployments only.
  3. 3An HTTP request hits the preview URL's health path and captures status code and response time.
  4. 4A logic step decides pass (2xx within the latency budget) or fail.
  5. 5A Slack message posts the review card — green for pass, red for fail — with the deploy URL, commit SHA, status code, and latency.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect VercelDeploys, runtime logs, analytics.
  2. 2
    Connect HTTP webhookTrigger any URL on agent actions.
  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.