DEVOPS
Page on-call for a Sentry spike with the suspect deploy attached
When Sentry detects an error-rate spike, it correlates the timing with recent Vercel deployments and opens a PagerDuty incident enriched with the most likely culprit release…
How it runs
The automated pipeline, trigger to output.
- TriggerSentry error-spike alert webhookSentry
- ActionQuery Vercel deploys around the spike start timeVercel
- LogicRank and select most likely culprit release
- ActionOpen PagerDuty incident with suspect releasePagerDuty
- OutputAppend commit, author, and deploy link to incidentPagerDuty
What it does
Turns a noisy Sentry spike alert into an actionable page. When Sentry fires a metric or issue alert, the flow looks up Vercel deployments around the spike's start time, picks the deploy that most likely introduced it, and opens a PagerDuty incident that already names the suspect release, commit, and author so the responder starts with a hypothesis instead of a blank page.
When to use it
Use it when your on-call gets paged for error spikes but has to manually dig through the deploy log every time to figure out what changed. This front-loads that correlation into the incident itself.
How it works
- 1A Sentry alert webhook fires for an error-rate or issue spike.
- 2The flow reads the spike start time and affected project from the payload.
- 3It queries Vercel for production deployments in the minutes before the spike.
- 4Logic ranks candidates by proximity and selects the most likely culprit.
- 5It opens a PagerDuty incident titled with the issue and suspect release.
- 6It appends the commit, author, and deploy link as incident context.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect VercelDeploys, runtime logs, analytics.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 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.