Hookbase Blog

Hookbase is now an installable PWA: a standalone dashboard window, home-screen icon, and jump-list shortcuts, plus a branded offline shell that deliberately never caches stale webhook or delivery data.

Webhooks are not an ordered stream. Retries, parallel senders, and network variance scramble arrival order. Here is why it happens and the handler patterns that make it a non-issue.

A single provider event usually needs to reach your warehouse, Slack, an internal service, and a queue at once. Skip the fan-out service — do it declaratively with one source and many routes, each with its own filter, transform, and destination.

Transient failures are inevitable, so retries are non-negotiable. Learn exponential backoff, jitter, retry budgets, idempotency, and dead-letter queues — and how a relay handles outbound retries so your endpoint just stays fast and idempotent.

Route webhook events from Stripe, GitHub, Shopify, or any provider straight into your data warehouse. Hookbase batches events into S3, R2, GCS, or Azure Blob — ready to load into Snowflake, BigQuery, and Databricks, or query in place with Athena and Redshift Spectrum.

The clusters page, replay-with-edit modal, and pattern hints we shipped over the last three weeks are all the same loop: triage → probe → fix → confirm → fan out. Today that loop is callable from MCP, so any AI assistant can drive recovery end to end.

Failure clusters last week told you what failure patterns exist. They didn't tell you which one is on fire right now. Two new rate windows split clusters into "active incidents" (escalating) and everything else — so when you arrive during an incident, the page tells you where to look.

A hand-curated library of 12 common webhook failure patterns matches every failed delivery in microseconds — likely cause and suggested fix appear before any AI call. Alongside it, a new Recent Changes tab pulls every audit log entry for the route/destination/transform involved in the failure over the last 14 days.

You shipped a bad transform. You don't notice for 17 minutes. By the time you revert, hundreds of events have failed against the broken code. The events page bulk action now accepts the same override matrix as per-delivery replay — fix the transform once, apply the fix to every event in the window, optionally save the new code to the route.

When something breaks in webhook land, it breaks in waves. Every failed delivery now gets a normalized fingerprint — same root cause, same hash — and a new Failure Clusters page groups the wave into one row. Click any cluster to inspect a sample and replay every matching delivery with one override.

The transform builder always made you edit against a sample input you made up. The new Failures tab pulls the last 10 events that actually failed on a given route and runs your in-progress code against each — pass/fail status, expandable per-event output, debounced auto-rerun as you edit.

Until now, "why didn't this route fire?" required pulling up the route, reading the filter conditions, reading the event payload, and mentally evaluating the expression. The new Routes tab on the event debugger renders the per-clause pass/fail breakdown for every active route on the event's source — same code path as the live ingest evaluator.

Plain replay re-runs the same broken inputs against the same broken destination — guaranteed to fail the same way unless the failure was transient. Today every failed delivery gets an Edit & Replay modal: change the payload, the transform code, the destination, or the outbound headers for this one retry, all optional.

The topology view used to be a static Mermaid render that kept erroring out on perfectly valid input. It is now a pan / zoom / drag canvas built on React Flow with dagre auto-layout — interactive, dark-mode aware, and stable across every diagram we have thrown at it.

Anomaly detection learns each source's normal traffic pattern and alerts when volume spikes or drops vs. that baseline. Schema drift auto-infers a JSON schema from observed payloads and tells you the moment a provider adds, removes, or retypes a field. Both ship today on Pro and Business.

The new hookbase init command scaffolds a working webhook handler in any of five frameworks. hookbase listen filters tunnel traffic before it reaches localhost. And hookbase trigger now signs payloads using the live provider catalog. Three additions, one upgrade.

The new hookbase/setup-tunnel GitHub Action exposes a localhost port via a public Hookbase tunnel during CI runs. Receive real webhooks from Stripe, GitHub, Shopify, or any provider against ephemeral test environments — without managing tunnel lifecycle by hand.

Shopify HMAC verification trips up almost every first-time integrator. Here is exactly how the signature is computed, what goes wrong, and a working implementation in Node, Python, Go, and Ruby.

Stripe retries for 3 days. GitHub gives up after one failure. Shopify retries 19 times. Knowing the rules for each provider is the difference between losing events and not. A reference table plus what it means for your handler.

Webhooks get retried. Without idempotency, that means duplicate orders, double charges, and angry customers. Here is how to design a deduplication strategy that actually works.

Not every provider signs webhooks. When the provider hands you an unauthenticated POST, you have to invent your own security model. Here are the providers, the reasons, and three patterns that work.

A reference of the headers used by Stripe, GitHub, Shopify, Twilio, Slack, Plaid, Square, and more — including event ID, signature, event type, and the quirks for each.

You wired up a webhook, the signature check fails on every request, and you have no idea why. Here is the systematic checklist that finds the bug in under five minutes.

Webhook timeouts cascade into duplicates, missed events, and angry providers throttling your endpoint. Here is what actually causes them and the fixes that hold up under real traffic.

Stripe CLI, ngrok, and Hookbase tunnel — the three options for testing Stripe webhooks against your local dev server, with the tradeoffs that matter when you actually use them.

Webhooks are not always the right answer. Polling has been quietly winning back ground in some scenarios. Here is a practical decision framework, with the tradeoffs that matter at scale.

Three ways to receive GitHub webhooks on your local machine for development — including the one that does not require an ngrok account, a public URL, or punching holes in your firewall.

Skip the HTTP middleman. Hookbase now delivers webhooks straight to AWS SQS, EventBridge, Google Cloud Pub/Sub, Azure Service Bus, and OCI Queue — with full retry and circuit breaker support.

Find any webhook by what it contains, not just its metadata. Full-text and field-level search across your event payloads — a feature no other webhook platform offers.

Manage your entire webhook pipeline — inbound and outbound — with Terraform. 9 resources, full CRUD, import support, and the only provider that covers both directions.

Get a unique webhook URL instantly. No signup required. Inspect headers, body, and metadata in real-time with code generation, type inference, and custom responses.

Hookbase now exports webhook delivery traces and metrics to your existing observability stack via OpenTelemetry. See your webhook pipeline health in Grafana, New Relic, Honeycomb, or Axiom — no collector required.

Hookbase now ships pre-built integration templates that create your entire webhook pipeline -- source, destination, transform, filter, and route -- in a single click. Start with Stripe to Slack, GitHub to Discord, and eight more.

Ship a customer-facing webhook management UI in minutes. The new Hookbase Portal gives your users self-service control over endpoints, subscriptions, testing, and delivery history -- embedded in your app or hosted for you.

Describe your transform in plain English and let AI generate JSONata, JavaScript, or Liquid code. Load sample payloads, auto-validate, and test before saving.

Schedule a one-time webhook delivery for a specific date and time. Set the URL, payload, and schedule -- Hookbase handles the rest with retries and status tracking.

Hookbase tunnels now support bidirectional traffic. Send HTTP requests from your local machine through Hookbase to reach internal APIs, IoT devices, and services behind firewalls.

We have increased maximum webhook payload sizes across all plans -- up to 10 MB on Business. Handle EDI documents, batch events, and large payloads without hitting limits.

JavaScript transforms are now executed inside a QuickJS WebAssembly sandbox with memory isolation, CPU time limits, and no network access. Same API, stronger security.

Hookbase now offers static IP delivery for outbound webhooks. Whitelist one IP address in your firewall and receive all webhook traffic through a dedicated, fixed endpoint.

Hookbase now supports warehouse destinations. Route webhook events directly to Amazon S3, Cloudflare R2, Google Cloud Storage, or Azure Blob Storage as structured JSONL or JSON files with automatic batching, field mapping, and encrypted credentials.

New per-source Transient Mode skips payload storage entirely. Designed for HIPAA, GDPR, and data minimization requirements in webhook pipelines.

Manage webhook sources, destinations, routes, and tunnels as native Kubernetes CRDs. GitOps-ready with Helm, sidecar injection, and drift detection.

An honest comparison of Hookbase and Webhook Relay covering features, pricing, transforms, and use cases to help you pick the right webhook platform.

Manage webhooks from Python with the official Hookbase SDK. Sync and async clients, Pydantic models, webhook verification, and full API coverage in a single pip install.

Mock mode lets you configure custom responses for destinations during testing. Simulate errors, latency, and validate transforms before going live.

Meet your new AI-powered webhook expert. Create sources, destinations, routes, and cron jobs just by describing what you need.

Export your route configurations as portable JSON and import them anywhere. Perfect for staging-to-production deployments, backups, team collaboration, and disaster recovery.

Build powerful webhook transformations without writing code. Our new visual builder generates production-ready JSONata with drag-and-drop simplicity.

Automatically prevent duplicate webhook processing with intelligent deduplication strategies. Works out-of-the-box with Stripe, GitHub, Shopify, and 10+ providers.

Learn how to transform webhook payloads on the fly using Hookbase's powerful transformation engine. Support for JSONata, JavaScript, Liquid templates, and XSLT.

Learn what webhook relay is, how it works, and why you need it for building reliable webhook integrations. Complete guide with examples.

Learn how to handle Stripe webhooks reliably in production. Best practices for verification, idempotency, error handling, and more.

Complete guide to webhook security. Learn about signature verification, IP allowlisting, rate limiting, and other security best practices.

Hookbase now supports 6 notification channel types including Slack, Microsoft Teams, Discord, PagerDuty, Email, and Custom Webhooks. Get instant alerts when webhook deliveries fail.