SECOPS
On-Demand Repo Secret Audit with Shareable Report
Triggered manually for a chosen repository, it deep-scans full git history for secrets and delivers a formatted findings report to a Google Drive folder for the team.
How it runs
The automated pipeline, trigger to output.
- TriggerOperator starts audit for a repo
- ActionClone full repo historyGitHub
- ActionScan all commits for secrets
- LogicGroup and dedupe findings
- ActionGenerate formatted report
- OutputSave report to Google DriveGoogle Drive
What it does
This workflow runs an on-demand, deep secret audit of one repository you pick, scanning the entire commit history rather than just recent changes, then produces a clean findings report and drops it in a shared Google Drive folder.
When to use it
Use it before open-sourcing a repo, during vendor due diligence, or when onboarding a newly acquired codebase. It is the manual, thorough counterpart to the always-on scanners, meant for a point-in-time review you can hand to stakeholders.
How it works
- 1An operator manually starts the run and selects the target repository.
- 2An action clones the full history of the chosen GitHub repo.
- 3Every commit is scanned for credential patterns across all branches.
- 4A logic step groups findings by file and severity and strips duplicates.
- 5A formatted report is generated with each finding's location and recommended action.
- 6An output saves the report to a shared Google Drive folder for review.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect Google DriveDocs, sheets, slides, files.
- 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.