SECOPS
Gate GitLab MR merge until the assigned security reviewer acknowledges
Blocks a security-labeled merge request from being mergeable until the assigned reviewer clicks an acknowledgment in Slack, then flips the GitLab approval so merge can proceed.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab security-labeled MR opened or updatedGitLab
- ActionApply blocking approval rule in GitLabGitLab
- ActionSend Slack acknowledgment request to reviewerSlack
- LogicBranch on Acknowledge vs Request-changes
- ActionRecord approval and clear gate in GitLabGitLab
- OutputPost sign-off confirmation to SlackSlack
What it does
A security label should mean a human actually looked, not just that a label exists. This workflow holds an MR in a non-mergeable state (via a blocking GitLab approval rule) until the assigned reviewer explicitly acknowledges in Slack, then releases the gate.
When to use it
Use it when compliance requires provable security sign-off before merge, and you want the acknowledgment captured as an auditable event rather than a casual thumbs-up.
How it works
- 1A GitLab webhook fires when an MR carrying a `security::*` label is opened or updated.
- 2An action applies a blocking approval rule and sets the MR to draft-blocked status in GitLab.
- 3A Slack interactive message goes to the assigned reviewer with Acknowledge and Request-changes buttons.
- 4A logic step waits for the button response and branches on the choice.
- 5On acknowledge, an action records the approval in GitLab and clears the blocking rule.
- 6A Slack confirmation posts to the channel with the reviewer name and timestamp.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect SlackChannels, DMs, threads, mentions.
- 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
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.
Post-Revocation Verification and Audit Logging
After a key is revoked, it confirms the old credential actually fails, verifies the replacement works.
Exposed-Secret Incident Triage and Remediation Agent
An agent-driven workflow that investigates a reported leaked secret end to end, decides revoke-versus-escalate, executes the rotation.
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.
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.