SECOPS
Attach Sentry production risk context to security MR reviews
When a security-labeled MR touches files tied to recent Sentry errors, it pulls those issues and comments the production risk profile directly on the MR so reviewers weigh…
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab MR gains a security labelGitLab
- ActionFetch MR changed file pathsGitLab
- ActionQuery Sentry issues for those pathsSentry
- LogicAssess whether production risk exists
- OutputComment risk profile on the MRGitLab
What it does
Links code review to production reality. For a security-labeled merge request, it maps the changed files to Sentry issues seen in the last 30 days and posts a comment summarizing open errors, event volume, and affected releases for those code paths, so reviewers know which sensitive areas are already shaky.
When to use it
Use it when security reviews happen in a vacuum and approvers cannot tell whether a touched module is rock-solid or already throwing in production. Especially useful for auth and payment paths where instability plus a sensitive change is a compounding risk.
How it works
- 1A GitLab webhook fires when a security label is added to an MR.
- 2The flow fetches the MR's changed file paths.
- 3It queries Sentry for issues whose stack frames reference those paths in the recent window.
- 4A branch decides whether any meaningful production risk exists.
- 5If issues are found, it posts a GitLab MR comment ranking the riskiest files with error counts and links back to each Sentry issue; if clean, it posts a short all-clear note.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect SentryErrors, performance, releases.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More SecOps workflows
Post-Revocation Verification and Audit Logging
After a key is revoked, it confirms the old credential actually fails, verifies the replacement works.
Page on-call when a WAF rule mass-blocks legitimate traffic
On demand or every few minutes, it detects a single Cloudflare WAF rule suddenly blocking a broad spread of ASNs and paths (a likely false-positive storm).
PII Content Scan on New Dropbox External Share
When a file gets an external Dropbox link, it reads the file content, uses an AI classifier to detect PII or secrets.
Compile a weekly WAF tuning review with trends to Confluence
Every week an agent rolls up Cloudflare WAF block clusters by rule and ASN, compares them to prior weeks for trend direction.
Sensitive Dropbox Link Owner Remediation Loop
When a newly created Dropbox shared link points to a sensitive file, this workflow DMs the file owner, gives them a deadline to justify or revoke it.
GitLab Push Secret Detection to Block and History Purge
On a GitLab push that contains a detected secret, it revokes the exposed credential, opens a tracking issue with git-history purge instructions.
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.