SECOPS
Rotate Leaked Cloudflare Token on GitHub Secret-Scan Alert
When GitHub secret scanning flags a leaked Cloudflare API token in a repo, it automatically rolls the token at Cloudflare, swaps the new value into the repo's Actions secrets.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub secret-scanning alert receivedGitHub
- LogicFilter: alert is a Cloudflare API token
- ActionCreate new Cloudflare token, revoke leaked oneCloudflare
- ActionUpdate repo Actions secret with new tokenGitHub
- OutputPost rotation receipt to SlackSlack
What it does
Closes the loop between detection and remediation for a single high-blast-radius credential type: Cloudflare API tokens. The moment GitHub's secret scanning fires an alert for a Cloudflare token, this workflow mints a fresh token, invalidates the exposed one, updates the GitHub Actions secret so CI keeps working, and records exactly what happened.
When to use it
Use it when your team ships Cloudflare automation from GitHub and you cannot afford the hours between a leak alert and a human rotating the key by hand. Best for orgs where Cloudflare tokens gate DNS, WAF, or Workers deploys.
How it works
- 1GitHub secret-scanning alert webhook fires with the detected secret type.
- 2A filter confirms the alert type is a Cloudflare API token; anything else exits.
- 3Cloudflare creates a replacement token with the same scopes, then revokes the leaked one.
- 4The new token value is written back into the repo's GitHub Actions secret.
- 5A Slack message delivers the rotation receipt: repo, alert URL, old token id revoked, and timestamp.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 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
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.