SECOPS
Block GitLab merge request on secret and rotate if already pushed
Inspects each GitLab merge request for credentials, fails the MR check when one is found.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab merge request opened or updatedGitLab
- LogicScan MR diff for credentials
- ActionSet MR check to failed to block mergeGitLab
- LogicBranch: secret already on a pushed branch?
- ActionRotate Vercel value and revoke old keyVercel
- OutputOpen ClickUp remediation taskClickUp
What it does
Reviews every GitLab merge request for hardcoded credentials before merge. If a secret is found it fails the MR check to block the merge, and if that secret has already been pushed to a remote branch it treats the leak as live, rotating the Vercel environment value and opening a tracked remediation task.
When to use it
Use this on GitLab teams that gate merges with checks and want prevention plus response in one flow. It stops new leaks at review time while still rotating anything that already touched a remote, so a blocked MR never leaves a live exposed key behind.
How it works
- 1A GitLab merge request event fires with the diff and source branch.
- 2A scan step checks the changes for credential signatures.
- 3A branch routes clean MRs to a pass and flagged MRs onward.
- 4The MR check is set to failed so the merge is blocked.
- 5A second branch tests whether the secret already exists on a pushed remote branch.
- 6If so, Vercel rotates the affected value and revokes the old key.
- 7A ClickUp task is created with the MR link, author, and rotation outcome.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect VercelDeploys, runtime logs, analytics.
- 3Connect ClickUpDocs + tasks + chats in one workspace.
- 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 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.