SECOPS
Pull Request Secret Gate with Purge Tracking
Scans every opened pull request for hard-coded secrets, blocks merge when one is found, and opens a purge task to rotate the key and scrub it from history.
How it runs
The automated pipeline, trigger to output.
- TriggerPull request opened or updatedGitHub
- LogicScan PR diff for secrets
- LogicConfirm finding is a real credential
- ActionSet failing status to block mergeGitHub
- ActionOpen rotation and purge taskClickUp
- OutputNotify security channelSlack
What it does
Stops secrets at the gate. On each new pull request it scans the diff, and if a credential is present it marks the PR check as failed so it cannot merge, comments exactly which lines are offending, and spins up a remediation task covering both rotation and git-history scrubbing.
When to use it
Use it as a required status check on protected branches. Catching the secret in review is cheaper than revoking after merge, and the purge task ensures the leaked value is rotated even though it briefly existed in the PR.
How it works
- 1A GitHub pull_request webhook fires when a PR is opened or updated.
- 2A scan step checks the PR diff for known secret patterns and entropy spikes.
- 3A logic gate decides whether any finding is a real credential.
- 4On a hit, the flow sets a failing commit status to block the merge.
- 5It posts a review comment pinpointing the offending file and lines.
- 6It opens a ClickUp task to rotate the key and purge it from history, then notifies Slack.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect ClickUpDocs + tasks + chats in one workspace.
- 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 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.