Destination

A destination is a target where Hooksbase delivers events. Each webhook can have multiple destinations; routing rules decide which single destination handles each event.

A destination is more than just a URL. It includes:

• The target — a URL for HTTP destinations, or a configuration block for typed destinations
• Auth/configuration — custom headers for HTTP destinations, or credentials and protocol settings for typed destinations
• Enabled or paused status — turn destinations off without deleting them

Typed destinations

Beyond standard HTTP webhooks, Hooksbase supports typed outbound destinations that speak the protocol of common downstream systems:

• HTTP — POST to a configured URL
• AWS SQS — SendMessage to a queue
• AWS EventBridge — PutEvents to an event bus
• GCP Pub/Sub — publish to a topic
• S3-compatible object storage — write the event payload as an object

Typed destinations let the relay deliver directly to your existing infrastructure without an intermediate HTTP layer.

Why multiple destinations per webhook

The pattern that ships in production: different source events need different handoff paths. A payment_failed event might go to:

• An agent at your application's HTTP endpoint
• An SQS queue for analytics
• A Slack channel via an HTTP destination
• An audit log in S3

All four can be destinations on the same webhook. Routing rules decide which one is selected for a given event; the default destination handles events no rule matches.

This is routing, not relay-level fan-out. For one event to reach multiple independent consumers, route to a broker or service that fans out downstream.

For the routing model in detail: Route events to the right agent.