ENGINEERING
Watch Sentry for new errors after a security-labeled MR merges
When a security-labeled merge request merges, this opens a timed watch on Sentry and, if new or spiking errors appear within the window, posts a regression alert to Slack tagging…
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab webhook: security-labeled MR mergedGitLab
- LogicRecord merge time + author, open watch window
- ActionQuery Sentry for new or spiking issues since mergeSentry
- LogicBranch: did a qualifying issue surface?
- OutputPost regression alert to Slack tagging the authorSlack
What it does
After a merge request carrying a security label merges to the release branch, it starts a post-deploy watch on Sentry scoped to the affected project. For the watch window it checks for newly surfaced issues or error-rate spikes, and if it sees one it raises a regression alert that links the Sentry issue back to the merged MR and tags the author.
When to use it
Use it when security fixes occasionally introduce regressions and you want a tight feedback loop tying production errors back to the exact change that shipped them — without an engineer babysitting the Sentry dashboard after every merge.
How it works
- 1A GitLab webhook fires when a security-labeled MR merges.
- 2The flow records the merge time and the MR author, then opens a watch window.
- 3It queries Sentry for issues first seen or spiking after the merge timestamp in the relevant project.
- 4A branch checks whether the window surfaced any qualifying issue.
- 5If so, a Slack regression alert posts with the Sentry issue link, the MR, and an @-mention of the author.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 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 Engineering workflows
Gate breaking API PRs behind downstream consumer acknowledgement
When a PR introduces a breaking contract change, comments the impact summary back on the PR, applies a blocking label.
Publish a versioned API changelog to Confluence on each release tag
On a new semver release tag, gathers the contract changes since the last release and writes a clean.
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Upgrade Impact Router to Module Code Owners
Maps a dependency-bump PR's affected modules to their CODEOWNERS, then DMs each owner on Slack with only the changelog slice that touches code they own.
Re-Voice IVR Prompts on Phone-Tree Config Merge
When a phone-tree config change merges in GitHub, regenerates the ElevenLabs audio for any prompt whose script changed in the diff and opens a follow-up PR adding the new audio…
Upstream Release to Notion Upgrade Brief
When a watched package publishes a new release, fetches the release notes, maps them to the internal modules that depend on it.
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.