Deliver Webhooks Anywhere — Not Just HTTP
Most webhook relays can only POST to a callback URL. Hookbase does that too — and can also write events directly into object storage or publish them onto a managed queue, so you don't have to build and run a consumer just to get webhook data where it belongs.
Three Kinds of Destination, One Pipeline
A destination is simply where a routed event ends up. Everything Hookbase does on the way there — signature verification, filtering, transforms, retries, and delivery logging — works the same regardless of which kind you pick. See how the webhook relay works for the full picture; this page covers where the events can land.
HTTP Endpoints
The classic option. Forward the event to any URL with custom headers, auth, timeouts, and automatic retries on failure.
Object Storage
Batch events into files and write them to a bucket. The cheap, durable way to keep a complete history you can query later.
Message Queues
Publish onto a queue or event bus your services already consume, so webhook traffic joins your existing event-driven architecture.
Stream Webhooks Into Object Storage
Point a destination at a bucket and every routed event is batched into files and written there. Because the files are partitioned JSONL, they drop straight into whatever you already query with — Athena, BigQuery, Snowflake, DuckDB, or plain scripts — without any ingestion service in between. Useful for analytics, long-term audit archives, and replaying history after your retention window has passed.
Amazon S3
Write batched events straight into an S3 bucket. Configure region, credentials, path prefix, JSONL or JSON output, date/hour/source partitioning, and optional gzip compression.
Cloudflare R2
Land webhook data in R2 using the S3-compatible API — point at your account endpoint with an R2 API token and get the same prefixes, partitioning, and file formats.
Google Cloud Storage
Deliver to a GCS bucket with a service account key. Supports path prefixes, JSONL or JSON array files, partitioning, and gzip compression for cheaper storage.
Azure Blob Storage
Write into an Azure Blob container using a storage account name and key. Same prefix, file-format, and partitioning controls as the other storage targets.
Publish Webhooks Onto Your Queues
If your services already talk to each other over a queue or event bus, an HTTP callback is an awkward front door — it makes you run a public endpoint whose only job is to turn a request back into a message. Hookbase publishes the event directly instead, so a provider outage or a traffic spike becomes queue depth rather than dropped webhooks.
AWS SQS
Push events onto a standard or FIFO queue by URL and region. Set a message group ID for FIFO ordering and let your existing consumers drain the backlog at their own pace.
AWS EventBridge
Publish onto an event bus with a configurable source and detail-type, so webhook traffic flows through the same rules and targets as the rest of your AWS events.
GCP Pub/Sub
Publish to a Pub/Sub topic with a project ID and service account key. Fan the same webhook out to every subscription attached to the topic.
Azure Service Bus
Send to a Service Bus queue or topic using a namespace and shared access key — useful when the consuming workloads already live in Azure.
OCI Queue
Deliver to an Oracle Cloud Infrastructure queue by queue ID, region, and endpoint with a pre-generated auth token.
Batching and Field Mapping
Storage and queue destinations don't have to send one event at a time. Both support batching, and storage destinations can reshape the payload before it lands.
Batch Size
Set how many events accumulate before a batch is flushed — from a single event up to 1,000, defaulting to 100. Larger batches mean fewer, bigger files and fewer API calls.
Flush Interval
A time window (0–300 seconds, defaulting to 30) that caps how long a partial batch waits. Low-volume sources still flush on schedule instead of sitting until the batch fills.
Field Mapping
For storage destinations, map fields out of the raw payload into a flat, typed record — pick a source path, a target column name, a type, and an optional default value.
Example field mapping
Paste a sample payload and Hookbase will detect the available fields for you. The result is a predictable set of columns in your bucket instead of deeply nested provider JSON, so downstream queries don't break when a provider adds a field.
Why This Matters
Most hosted webhook relays stop at the HTTP callback. That leaves the last mile to you.
A typical HTTP-only relay
Hookbase
Object storage and queue destinations are available on the Pro and Business plans. HTTP destinations are included on every plan, including the free tier.
Send Your Webhooks Where They Actually Need to Go
Create a source, add a destination, and pick a bucket, a queue, or a URL. Get started free — no credit card required.
Start Free