SECOPS
Cloudflare Token Leak Revoke and Lockdown
On a webhook reporting a leaked Cloudflare API token, this workflow revokes the token, blocks the abusing source IP at the WAF.
How it runs
The automated pipeline, trigger to output.
- TriggerInbound leak-report webhookHTTP webhook
- LogicValidate payload and resolve token scopes
- ActionRevoke Cloudflare API tokenCloudflare
- ActionAdd WAF block rule for source IPCloudflare
- OutputNotify security channel in SlackSlack
What it does
Contains a leaked Cloudflare API token before it can be abused: it kills the token, slams the door on any IP already using it via a WAF rule, and tells the team exactly what scopes were exposed.
When to use it
Use it when Cloudflare tokens are part of your attack surface and a leak detector (vendor alert, honeypot, or scanner) can POST a finding. Ideal when revocation alone isn't enough and you also want to block live exploitation.
How it works
- 1An inbound webhook delivers the suspected token, its ID, and any observed source IP.
- 2A logic step validates the payload and looks up the token's scopes to gauge impact.
- 3An action revokes the token through the Cloudflare API.
- 4If a source IP was observed, an action adds a WAF block rule for that IP.
- 5The workflow outputs a Slack alert listing the revoked token, its scopes, and the firewall action taken.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent 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
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.