DEVOPS
Post-Deploy Smoke-Check Summary
After a Vercel production deploy, runs Datadog Synthetic smoke checks against the new build and posts a pass/fail summary to Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel deployment succeededVercel
- ActionTrigger Datadog Synthetic smoke tests against deploy URLDatadog
- LogicPoll results and aggregate pass/fail countsDatadog
- LogicBranch on overall health (all passed vs. any failed)
- OutputPost smoke-check summary to Slack channelSlack
What it does
Watches for successful production deployments on Vercel and immediately runs a smoke-check pass against the live build. It triggers your Datadog Synthetic tests for the critical paths (homepage, login, checkout, key API endpoints), waits for the results, and then posts a single, readable summary to Slack: which checks passed, which failed, response times, and a direct link back to the deployment. No more wondering whether the deploy that just went out is actually serving real traffic correctly.
When to use it
Use this when you ship to production frequently and want fast confirmation that a deploy is healthy without anyone manually clicking through the app. It is ideal for teams practicing continuous deployment who need a tight feedback loop: the moment Vercel reports a deploy as ready, the workflow confirms the site is actually up and the golden paths work. Pair it with an on-call rotation so a failed smoke check turns into an immediate, actionable Slack alert instead of a customer complaint hours later.
How it works
A Vercel deployment-succeeded webhook starts the run and hands over the deployment URL and metadata. The workflow calls the Datadog API to trigger your designated Synthetic smoke tests against that URL, then polls until all results are in. It aggregates the outcomes — counting passes and failures, capturing latency and any error detail — and branches on the result. Either way it formats a compact summary (status emoji, per-check breakdown, deploy link) and sends it to your chosen Slack channel, flagging the message clearly when any check fails so the right people see it first.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect DatadogMetrics, traces, log search.
- 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.
