SECOPS
Rotate a leaked Cloudflare API key and invalidate active sessions
On a manual incident trigger, this workflow rolls the exposed Cloudflare API key, purges cached edge tokens, and writes an audit record to Postgres before notifying the team.
How it runs
The automated pipeline, trigger to output.
- TriggerOperator starts rotation with exposed key ID
- ActionRoll Cloudflare API key and revoke the old oneCloudflare
- ActionPurge sessions and cached edge tokensCloudflare
- ActionInsert audit record into PostgresPostgres
- OutputConfirm rotation complete in SlackSlack
What it does
Gives an operator a one-click way to retire a compromised Cloudflare API key. It generates a new key, invalidates the sessions and cached tokens tied to the old one, and persists a tamper-evident audit row before announcing the rotation.
When to use it
Use this when a Cloudflare key shows up in a paste, a screenshot, or a misconfigured CI log and you need a controlled, recorded rotation rather than a panicked manual scramble. The manual trigger lets the responder confirm scope before anything is destroyed.
How it works
- 1An operator starts the workflow manually with the exposed key ID and incident reference.
- 2The workflow calls Cloudflare to roll the API key and revoke the old credential.
- 3It triggers a session and cached-token purge so anything signed with the old key stops working.
- 4An audit record is inserted into Postgres with who, what, when, and the incident reference.
- 5A Slack notice confirms the new key is live and the old one is dead.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 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.