SECOPS
Nightly Org-Wide Repo Secret Sweep with Rotation Queue
On a nightly schedule, walks every repo in the GitHub org for secrets that slipped past push-time scanning, batches each finding into a rotation webhook call.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule fires
- ActionList all repositories in the GitHub orgGitHub
- LogicScan recent commits per repo for missed secrets
- ActionQueue exposed fingerprints to rotation webhookHTTP webhook
- OutputOpen consolidated Linear ticket per affected repoLinear
What it does
This workflow is the catch-all backstop. Once a night it enumerates all repositories in your GitHub org and scans recent history for secrets that real-time checks may have missed, then queues each finding for rotation and records them per repo in Linear.
When to use it
Use it to cover gaps: repos onboarded before push protection existed, force-pushes that bypassed the gate, or detector rules that improved after old commits landed. It gives you a daily clean-bill-of-health signal across the whole org.
How it works
- 1A nightly schedule triggers the sweep.
- 2An action lists every repo in the org via the GitHub API.
- 3A logic step scans each repo's recent commits and collects findings, skipping anything already quarantined.
- 4An HTTP webhook call submits the batch of exposed fingerprints to the rotation service.
- 5One consolidated Linear ticket per affected repo is opened summarizing the findings and rotation outcomes as the final output.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect HTTP webhookTrigger any URL on agent actions.
- 3Connect LinearIssues, projects, cycles, triage.
- 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.