DEVOPS
Watch new Vercel deploys for Sentry regression spikes
When a Vercel production deploy goes live, watches Sentry for a burst of new or regressed issues tied to that release and alerts the on-call channel if the error rate climbs past…
How it runs
The automated pipeline, trigger to output.
- TriggerVercel deployment succeeded (production)Vercel
- LogicKeep only production environment deploys
- ActionQuery Sentry for new/regressed issues in this releaseSentry
- LogicCompare post-deploy error rate vs baseline threshold
- OutputAlert on-call Slack channel with offending release and top issuesSlack
What it does
Links every production deploy to the error behavior that immediately follows it. After a Vercel deployment succeeds, it polls Sentry for issues first seen (or marked regressed) in the new release version and compares the post-deploy error rate to the pre-deploy baseline. If errors spike past your tolerance, it pings the on-call Slack channel with the offending release and top issues.
When to use it
Use it when you ship to Vercel several times a day and want an automatic early-warning system that ties a regression back to the exact release that caused it, instead of discovering it from customer reports.
How it works
- 1A Vercel deployment-succeeded webhook fires with the release SHA and environment.
- 2A filter keeps only production deployments.
- 3The flow queries Sentry for new and regressed issues scoped to that release version over the following window.
- 4A branch compares the post-deploy error count against the trailing baseline.
- 5If the spike exceeds the threshold, it posts the release, delta, and top three issues to the on-call Slack channel; otherwise it records an all-clear.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect SentryErrors, performance, releases.
- 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
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.
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…
Page on-call when a Hugging Face Space build is stuck or errored
Polls Hugging Face Space runtime status on a schedule and opens a PagerDuty incident when a Space sits in a build or error state past a deadline, with a Slack heads-up.
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.
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.
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.