CHATBOTS

Discord WAF False-Positive Triage from Ray ID

When a user posts a Cloudflare ray ID in a Discord support channel, the bot looks up the blocked request's WAF event, classifies whether it looks like a genuine false positive.

CategoryChatbots
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew message in Discord support channelDiscordDiscord
  • LogicExtract ray ID; skip if none present
  • ActionFetch firewall event for ray ID from CloudflareCloudflareCloudflare
  • LogicClassify event as false-positive vs maliciousOpenAI
  • OutputReply in Discord thread with verdict and ruleDiscordDiscord

What it does

Turns a raw Cloudflare ray ID dropped in your Discord support channel into an instant, evidence-backed triage reply. The bot fetches the matching firewall event, shows which WAF rule fired, and tells the reporter whether their request looks like a legitimate block or a probable false positive.

When to use it

Run this when customers or internal users keep pasting "I got blocked, ray ID 8a1b..." into Discord and your on-call has to manually dig through the Cloudflare dashboard every time. It collapses that lookup into a single automatic reply.

How it works

  1. 1A message in the designated Discord support channel triggers the flow.
  2. 2A filter extracts a Cloudflare ray ID pattern from the message text; messages without one are ignored.
  3. 3The bot queries Cloudflare's firewall events API for that ray ID to retrieve the action, matched rule, source IP, and URI.
  4. 4A classifier scores the event as likely-false-positive or likely-malicious using the rule category and request shape.
  5. 5The bot posts a threaded reply summarizing the verdict, the rule that fired, and recommended next step.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect DiscordCommunity channels + voice + bots.
  2. 2
    Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
  3. 3
    Connect OpenAIModels, embeddings, files.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.