SECOPS
Datadog anomaly to Cloudflare managed-challenge proposal
Triggers when a Datadog monitor flags an origin request-rate or error anomaly, correlates it with Cloudflare edge data.
How it runs
The automated pipeline, trigger to output.
- TriggerDatadog monitor alert webhook firesDatadog
- ActionPull Cloudflare edge traffic for alert windowCloudflare
- LogicRank segments to find bot-heavy offender
- ActionDraft managed-challenge WAF ruleCloudflare
- OutputPost proposal linked to alert in SlackSlack
What it does
Uses Datadog as the surge detector instead of polling Cloudflare directly. When a Datadog monitor on origin request rate or 5xx errors fires, this flow pulls the matching window of Cloudflare edge traffic, isolates the bot-heavy segment, and proposes a managed-challenge rule for review.
When to use it
Ideal for teams that already run Datadog as their source of truth for service health. It ties an alert you already trust to a concrete Cloudflare mitigation, so the on-call engineer goes from "origin is hot" to "here is the exact rule to stop it" in one step.
How it works
- 1A Datadog monitor alert webhook triggers the flow with the anomaly time window and affected service tags.
- 2An action queries Cloudflare analytics for that same window, scoped to the zone serving the service.
- 3A logic step ranks segments by bot score and request volume to find the dominant offender.
- 4An action drafts a managed-challenge WAF rule targeting that segment (matched by path, country, or ASN).
- 5The proposal, linking back to the Datadog alert, is posted to Slack where approval triggers the Cloudflare ruleset update.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 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.