ENGINEERING
Daily Sentry cluster digest with batched GitLab issue creation
Runs each morning, groups the day's unresolved Sentry clusters by suspected owning team using blame data, and creates one batched GitLab issue per team plus a Slack summary.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled morning run
- ActionList 24h unresolved Sentry clustersSentry
- ActionMap top frames to owning team via blame + CODEOWNERSGitLab
- LogicGroup and rank clusters per team
- ActionCreate one batched GitLab issue per teamGitLab
- OutputPost cross-team digest to SlackSlack
What it does
Each morning it sweeps the unresolved Sentry issues from the last 24 hours, attributes each one to a likely owning team using GitLab blame and CODEOWNERS, and groups them. It then creates a single rolled-up GitLab issue per team listing their clusters by frequency, and posts a digest to Slack so leads see the day's error landscape at a glance.
When to use it
Use it when per-error issues create too much noise and you'd rather give each team one prioritized daily worklist. Good for organizations with multiple squads sharing one Sentry project who need ownership-based routing instead of a flat firehose.
How it works
- 1A scheduled trigger runs every morning.
- 2The flow lists unresolved Sentry issues from the trailing 24 hours with event counts.
- 3For each, it reads the top frame and maps the file to an owning team via GitLab blame and CODEOWNERS.
- 4It groups clusters by team and sorts each group by frequency.
- 5It creates one batched GitLab issue per team with the ranked cluster list.
- 6It posts a cross-team digest to Slack linking every issue created.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect GitLabRepos, MRs, pipelines, registry.
- 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
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…
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.
Scan for deprecated endpoints and email consumers a weekly sunset countdown
On a weekly schedule, scans the OpenAPI spec for endpoints marked deprecated with a sunset date, and emails each consuming team a countdown of how many days remain before removal.
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.
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.
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.