community-automations/webhook-triage

DevOps & Code

PublicClaude subagent

Webhook Triage

When dozens of services fire webhooks at one endpoint, a giant if-else block quickly turns into something nobody wants to touch. This triage layer sits in front and decides where each event belongs.

sonnet4 daysWebhookOpenAIRedisSlack
ClaudeClaude
ROI for
README.md

Why this subagent

When dozens of services fire webhooks at one endpoint, a giant if-else block quickly turns into something nobody wants to touch. This triage layer sits in front and decides where each event belongs.

It verifies the signature, parses the event, drops duplicates against a cache, and routes to the right handler. Anything it cannot place gets flagged in Slack instead of silently dropped. You get a clean dispatch log showing every decision and why it was made.

How it runs

    • 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.

Sample output

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.