CHATBOTS

Agentic WAF Investigator with Discord Approval Gate

An autonomous agent investigates a Discord-reported WAF block end to end: pulls Cloudflare logs, correlates with PagerDuty incidents, decides if an allowlist is safe.

CategoryChatbots
Enginepaperclip
Difficultyadvanced
Triggerevent
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerInvestigation request in DiscordDiscordDiscord
  • ActionFetch event and rule matches from CloudflareCloudflareCloudflare
  • ActionCheck PagerDuty for active incident on pathPagerDutyPagerDuty
  • LogicReason and draft allowlist or decline
  • OutputPost draft to Discord for human approvalDiscordDiscord
  • ActionOn approval, file change ticket in LinearLinearLinear

What it does

Hands a full WAF investigation to an agent. From a single Discord report it gathers the Cloudflare firewall event, checks PagerDuty for any active security incident on the same path, reasons about whether an allowlist is safe, and proposes a scoped rule. A human approves in Discord before the Linear change ticket is created.

When to use it

Use it for higher-stakes blocks where context matters: you want the bot to actively rule out an ongoing attack before recommending a bypass, not just pattern-match a single event. The Discord approval gate keeps a human in the loop.

How it works

  1. 1A WAF investigation request in Discord triggers the agent.
  2. 2The agent fetches the firewall event and recent matches for that rule from Cloudflare.
  3. 3It queries PagerDuty to confirm no active incident targets the same endpoint.
  4. 4The agent reasons over the evidence and drafts either a scoped allowlist or a decline with rationale.
  5. 5It posts the draft to Discord and waits for an explicit human approval reaction.
  6. 6On approval, it files the change as a Linear issue and links it back in Discord.

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 PagerDutyIncidents, on-call, escalations.
  4. 4
    Connect LinearIssues, projects, cycles, triage.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.