ENGINEERING
Sentry error spike to PagerDuty with blame-attributed GitLab issue
On a sudden Sentry event-rate spike, it pages on-call via PagerDuty and simultaneously files a GitLab incident issue naming the suspected deploy and commit from blame analysis.
How it runs
The automated pipeline, trigger to output.
- TriggerSentry event-rate spike metric alertSentry
- LogicCheck spike magnitude against severity threshold
- ActionTrigger PagerDuty incident to on-callPagerDuty
- ActionCorrelate spike time with recent GitLab deploysGitLab
- OutputCreate GitLab incident issue with rollback hintGitLab
What it does
Detects a sudden spike in a Sentry issue's event rate and treats it as a live incident. It pages the on-call engineer through PagerDuty and, in parallel, opens a GitLab incident issue that names the suspect commit and the deploy window it landed in, so responders arrive with a rollback candidate already identified.
When to use it
Use it for high-severity, time-sensitive errors where rate-of-change matters more than raw volume. Best for production-critical services where the on-call needs both an immediate page and a pre-built incident record pointing at the likely offending deploy.
How it works
- 1Sentry fires on a metric alert when an issue's event rate spikes.
- 2The flow checks the spike magnitude against a severity threshold to decide whether to escalate.
- 3If severe, it triggers a PagerDuty incident routed to the service's on-call.
- 4It correlates the spike start time with recent GitLab deploys to pick the suspect commit.
- 5It creates a GitLab incident issue with the trace, suspect deploy, and rollback hint, linked to the PagerDuty incident.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect GitLabRepos, MRs, pipelines, registry.
- 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.