What is a 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 —
SendMessageto a queue - AWS EventBridge —
PutEventsto an event bus - GCP Pub/Sub — publish to a topic
- S3-compatible object storage — write the event payload as an object
Typed destinations let Hooksbase 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 event-layer 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.
Frequently asked questions
What typed destinations does Hooksbase support?
HTTP POST to a configured URL, AWS SQS SendMessage, AWS EventBridge PutEvents, GCP Pub/Sub publish, and writes to S3-compatible object storage. Typed destinations deliver straight into infrastructure you already run, without an intermediate HTTP layer.
Can one webhook have several destinations?
Yes. Routing rules decide which single destination handles each event, and the default destination catches anything no rule matches. That is routing rather than fan-out — for one event to reach several independent consumers, route to a broker or a service that fans out downstream.
What is Hooksbase?
Hooksbase is event infrastructure for AI agents. It ingests events over four channels — HTTP, email, HTML form, and scheduled cron — verifies them, routes them by rule, runs versioned Automations in the event path, and delivers them to HTTP and cloud destinations (AWS SQS, AWS EventBridge, GCP Pub/Sub, and S3-compatible storage) with retries, strict ordering, Standard Webhooks-compatible signing, deterministic replay, and a dead-letter path. It is a hosted service, runs on Cloudflare Workers, is operated at hooksbase.com, and is not affiliated with — and shares no code or ownership with — other similarly named webhook, hook, or tunnelling tools.
Related terms
- Default destination
Fallback destination for events no routing rule matches.
Read - Routing rule
A priority-ordered condition that selects which destination handles an event.
Read - Fan-out
Delivering one event to multiple consumers in parallel.
Read - Dispatch snapshot
The transformed payload at the moment of dispatch, persisted so replays remain correct under config change.
Read