SECOPS
Auto-rotate a leaked GitHub token caught by secret scanning
When GitHub secret scanning flags a committed credential, this workflow revokes the exposed token, opens a tracking issue.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub secret-scanning alert webhookGitHub
- LogicFilter: new alert and auto-rotate secret type
- ActionRevoke token and resolve the alert in GitHubGitHub
- ActionOpen remediation issue with commit and detector detailsGitHub
- OutputPost leak timeline and rotation status to SlackSlack
What it does
Turns a GitHub secret-scanning alert into an immediate revoke-and-record response. The moment a token is detected in a commit, the credential is revoked, a remediation issue is filed, and the security channel gets a single message with the alert, the affected repo, and the rotation status.
When to use it
Run this when your org relies on GitHub Advanced Security secret scanning and you want the leaked credential dead before a human even opens the alert. Ideal for teams where commit-leaked PATs, deploy keys, or API tokens are the most common exposure.
How it works
- 1A GitHub secret-scanning alert webhook fires with the detected secret type, repo, and commit.
- 2A filter checks the alert is new and the secret type is one your policy auto-rotates.
- 3The workflow calls GitHub to revoke the token and mark the alert resolved.
- 4It opens a GitHub issue capturing the repo, commit SHA, detector, and revocation result for audit.
- 5A Slack message lands in the security channel summarizing the leak and confirming the credential is dead.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 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.