Default destination

A default destination is the fallback target for events no routing rule matches. Every webhook in Hooksbase has at most one default destination; named destinations are optional additions.

How default destinations interact with routing

When an event arrives, Hooksbase evaluates routing rules in priority order. If a rule matches, the event delivers to that rule's destination. If no rule matches, the event delivers to the default destination.

This gives you two patterns:

• Default-only — no routing rules; every event goes to one destination. Simplest setup; right for single-consumer flows.
• Default-plus-rules — most events go to the default destination; specific events match rules and route elsewhere. Right for "send ordinary events to the agent, but send high-priority events to a different escalation destination."

Because every Hooksbase webhook has a default destination, unmatched events have a catch-all path. Keep that default active and point it somewhere safe for inspection.

A practical example

A webhook receiving Stripe events with:

• Routing rule: event.type starts_with "invoice." → billing-agent destination
• Routing rule: event.type starts_with "customer." → crm-sync destination
• Default destination: general-handler

A payment_intent.succeeded event matches no rule and goes to general-handler. An invoice.payment_failed matches the first rule and goes to billing-agent. The default acts as the catch-all so nothing slips through silently.

For the routing pattern in practice: Route events to the right agent.