SECOPS
Daily bot-surge digest with rule-tuning recommendations
Each morning it summarizes the prior day's Cloudflare bot-traffic surges and rule decisions, flags rules that over- or under-fired.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily morning schedule fires
- ActionPull 24h surge events + rule hit-countsCloudflare
- LogicFlag over/under-tuned rules
- ActionDraft digest with threshold recommendations
- OutputPost to Slack and open Linear tuning taskLinear
What it does
Produces a once-daily retrospective instead of real-time alerts. It rolls up the previous 24 hours of bot-surge events and the rules that fired, identifies challenges or blocks that likely hit legitimate traffic, and recommends threshold adjustments — then files the work to act on it.
When to use it
Run this for ongoing hygiene of your Cloudflare bot-management posture. It's the feedback loop that keeps the real-time proposers accurate: a steady cadence of "these rules are too aggressive, these are too loose" without anyone manually combing through logs.
How it works
- 1A daily schedule triggers the report at a fixed morning hour.
- 2An action pulls the last 24 hours of bot-surge events and active rule hit-counts from Cloudflare.
- 3A logic step flags rules with abnormal challenge-solve rates or block volumes as over- or under-tuned.
- 4An action drafts a concise digest with specific threshold-change recommendations.
- 5An output posts the digest to Slack and opens a tracked tuning task in Linear so recommendations don't get lost.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect LinearIssues, projects, cycles, triage.
- 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.