Blog
Notes on reliable event infrastructure.
Product updates, architecture notes, and workflow patterns for teams building on Hooksbase.
The complete guide to idempotency keys (for webhooks and APIs)
An idempotency key is a unique value attached to a request that tells the receiver: if you've seen this key before, return the same response without doing the work again. Here is how it works in practice — and what breaks without it.
Your agent shouldn't only listen to HTTP
Email ingest, form ingest, file handling, and scheduled webhooks give AI agents more ways to be triggered — without asking you to build three different pipelines.
Why automation platforms need an event layer in front
Every automation platform gives you an HTTP trigger and calls it good. That's fine for a prototype. For production — verified providers, replay, DLQ, multi-channel ingest — you need an event layer in front of the workflow runtime.
Routing, transforms, and replay for AI agents
Event routing and payload transforms are only useful when failed agent events can be replayed deterministically — with the exact payload and destination they would have reached the first time.
Migrating from classical webhook delivery to agent event infrastructure
If you built an agent on top of a classical webhook stack (Svix, Hookdeck, custom), you've probably run into the places where the assumptions don't quite fit. Here's what changes when you switch.