I need a pattern for routing webhook events to different queues based on event type

A solid way to route webhook events to different queues by event type is to use a message router / dispatcher pattern.

Pattern overview

1. Receive the webhook
2. Validate and normalize the payload
3. Inspect the event type
4. Map the event type to a queue
5. Enqueue the message
6. Have workers consume from each queue

Simple routing model

Webhook -> Webhook Receiver -> Event Router -> Queue A / Queue B / Queue C

Example mapping:

• user.created → user-events-queue
• order.paid → billing-queue
• shipment.updated → shipping-queue
• unknown/default → dead-letter-queue or misc-queue

Example pseudo-code

QUEUE_MAP = {
    "user.created": "user-events-queue",
    "order.paid": "billing-queue",
    "shipment.updated": "shipping-queue",
}

def handle_webhook(request):
    event = parse_json(request.body)
    event_type = event.get("type")

    queue_name = QUEUE_MAP.get(event_type, "dead-letter-queue")
    enqueue(queue_name, event)

    return {"status": "accepted"}

Best practices

• Keep routing logic centralized in one router service/module.
• Use a default queue for unknown event types.
• Make processing idempotent using event IDs to prevent duplicate handling.
• Validate signatures before routing to ensure the webhook is authentic.
• Decouple webhook intake from processing so the endpoint responds quickly.
• Log routing decisions for debugging and observability.

More scalable option: topic-based routing

If your queue system supports it, you can publish all webhooks to a topic/exchange and let consumers subscribe with routing keys or filters.

Example:

• Routing key: event.user.created
• Routing key: event.order.paid

Then bind queues based on patterns:

• event.user.* → user queue
• event.order.* → billing queue

This works well with systems like:

• RabbitMQ
• AWS SNS + SQS
• Azure Service Bus topics
• Google Pub/Sub subscriptions

Recommended architecture

For most systems:

• Webhook receiver: validates and acknowledges
• Router: maps event.type to queue
• Dedicated queue per domain: billing, user, shipping, etc.
• Dead-letter queue: for unknown or failed events

If you want, I can also provide:

• a code example in Node.js / Python / Go
• a RabbitMQ / SQS / Kafka version
• or a full architecture diagram/pattern