community-automations/webhook-triage

DevOps 與程式碼

PublicClaude 子代理

Webhook 分流處理

當幾十個服務同時把 webhook 丟到同一個端點，那坨巨大的 if-else 很快就會變成沒人敢碰的燙手山芋。這個分流層擋在最前面，替每個事件決定它該去哪。

sonnet4 天WebhookOpenAIRedisSlack
ClaudeClaude
ROI for
README.md

為什麼選擇此子代理

當幾十個服務同時把 webhook 丟到同一個端點，那坨巨大的 if-else 很快就會變成沒人敢碰的燙手山芋。這個分流層擋在最前面，替每個事件決定它該去哪。

它會驗證簽章、解析事件、對照快取剔除重複，再把事件路由到正確的處理器。歸不了類的統統丟到 Slack 標記出來，而不是無聲無息地消失。你會拿到一份乾淨的派送紀錄，每個決定怎麼做的、為什麼這樣做，全都寫得清清楚楚。

運作方式

    • Read

      Used at step 01 to kick off the pipeline.

    • Write

      Used at step 01 to kick off the pipeline.

    • WebFetch

      Used at step 01 to kick off the pipeline.

    • WebSearch

      Used at step 01 to kick off the pipeline.

輸出範例

json
// Sample output
// (generated when the pipeline finishes)

Given a verified webhook payload, classify event type and urgency and return a JSON dispatch decision naming the target handler and dedupe key.

Unlock the rest

The full agent definition, install snippet, and starter task are gated for community members.

Members get the full `.md` agent file, the npm / pnpm install one-liners, a starter prompt that we've tuned against real runs, and the open-source repo when this automation ships there. One email, magic link, done.