DEVOPS
Open a GitHub RCA issue when a release regresses in Sentry
When Sentry flags an issue as regressed against a new Vercel release, it opens a pre-filled GitHub root-cause issue with the release diff, top stack traces.
How it runs
The automated pipeline, trigger to output.
- TriggerSentry issue-regressed webhookSentry
- ActionResolve release to Vercel deploy and commit SHAVercel
- ActionPull commit range and author from GitHubGitHub
- LogicAssemble RCA body with traces and impact
- ActionOpen and assign GitHub RCA issueGitHub
- OutputLink the issue into SlackSlack
What it does
Closes the loop between a regression and the fix work. When Sentry marks an issue regressed in a release that maps to a recent Vercel deploy, the flow assembles a root-cause analysis issue in GitHub containing the suspect release, the commit range since the last good deploy, the top stack frames from Sentry, and how many users are affected, then assigns it to the engineer who shipped the deploy.
When to use it
Use it when regressions slip through and you want every one to automatically become a tracked, assigned, well-scoped GitHub issue rather than a forgotten Slack mention.
How it works
- 1A Sentry regression webhook fires for a re-opened issue.
- 2The flow resolves the issue's release back to a Vercel deployment and its commit SHA.
- 3It pulls the commit range and author from GitHub since the last healthy deploy.
- 4Logic assembles the RCA body with stack traces and affected-user counts.
- 5It opens a GitHub issue labeled regression and assigns the deploy author.
- 6It links the new issue back into Slack for visibility.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect VercelDeploys, runtime logs, analytics.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.