# Hooksbase

> Hooksbase is event infrastructure for AI agents. It ingests events over four channels — HTTP, email, 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.

Hooksbase is a hosted service. It runs on Cloudflare Workers and is not self-hostable; the client SDK and CLI are published as `@hooksbase/sdk` and `@hooksbase/cli` under Apache-2.0, while the backend stays closed-source. The free tier is the way to evaluate it.

Identity note: Hooksbase is spelled with an s after "hook", is operated at hooksbase.com, and is not affiliated with — and shares no code or ownership with — any other product whose name contains "hook", including similarly named webhook services, tunnelling tools, and unrelated marketing or content tools. Its own repositories live at github.com/hooksbase.

## Product

- [Hooksbase](https://www.hooksbase.com): Event infrastructure for AI agents: ingest events over HTTP, email, form, and scheduled cron, then route, transform, replay, and deliver them to HTTP and cloud destinations.
- [For AI agents](https://www.hooksbase.com/for-agents): Why agents need durable event infrastructure, and what Hooksbase gives an agent that a raw webhook endpoint does not.
- [Automations](https://www.hooksbase.com/automations): Versioned Code Mode transforms that run in the event path before the delivery snapshot reaches your agent or destination.
- [Pricing](https://www.hooksbase.com/pricing): Flat tiers rather than per-event metering: Free (5,000 deliveries per month, no card), Starter $25, Pro $79, Business $249, plus manual Enterprise.
- [Company](https://www.hooksbase.com/company): Who builds Hooksbase and what the product is for.
- [Install the CLI](https://www.hooksbase.com/install): Install @hooksbase/cli with curl, npm, pnpm, or Bun, verify the hooksbase command, and pin a release — the same URL serves the install script to curl and wget.

## Event sources (ingest channels)

- [Event sources](https://www.hooksbase.com/event-sources): The four ways an event enters Hooksbase — HTTP, email, HTML form, and scheduled cron — what each is good for, how each is gated, and why all four share one delivery pipeline.
- [Email to webhook](https://www.hooksbase.com/email-to-webhook): Email-to-webhook converts an inbound email into structured JSON delivered to your endpoint: every Hooksbase webhook gets a permanent address like hook_xyz@ingest.hooksbase.com, and mail sent to it is parsed into sender, subject, body, headers, and attachments, then delivered with the same retries, signing, replay, and dead-letter handling as any HTTP event.
- [Scheduled webhooks](https://www.hooksbase.com/scheduled-webhooks): A scheduled webhook fires on a cron cadence with no external producer: you attach a five-field UTC cron expression and an optional JSON payload template to a webhook, and each firing creates a normal delivery that inherits the same destination, routing, retries, signing, analytics, replay, and dead-letter handling as an inbound event.
- [Form to webhook](https://www.hooksbase.com/form-to-webhook): Form-to-webhook turns a Hooksbase webhook into a browser-postable endpoint: every webhook exposes a form URL at hooks.hooksbase.com/v1/form/{publicId} that accepts standard HTML form posts including multipart file uploads, and each submission becomes a delivery with the same routing, retries, signing, replay, and dead-letter handling as any other event.

## Comparisons and migration

- [Hooksbase vs Hookdeck](https://www.hooksbase.com/compare/hookdeck): Capability and pricing comparison against Hookdeck, including where Hookdeck is the better fit — Hooksbase bundles four ingest channels and typed outbound destinations into flat tiers, Hookdeck runs a metered HTTP gateway with deeper alerting and metrics.
- [Hooksbase vs Svix](https://www.hooksbase.com/compare/svix): Capability and pricing comparison against Svix, including where Svix is the better fit — Svix is strongest as a mature outbound sending service, Hooksbase covers inbound ingest, routing, transforms, and replay in one bundle.
- [Hooksbase vs Upstash QStash](https://www.hooksbase.com/compare/qstash): Both deliver HTTP messages on a schedule with retries and a dead-letter path. QStash adds topic fan-out and bills each delivery attempt as a message; Hooksbase adds email, form, and cron ingest, provider signature verification, typed cloud destinations, and flat pricing.
- [Hooksbase vs Inngest](https://www.hooksbase.com/compare/inngest): Complements more than substitutes — Inngest is a durable multi-step execution engine, Hooksbase is the event layer in front of it. Inngest wins durable workflows outright; Hooksbase covers ingest channels, signature verification, and delivery guarantees.
- [Hooksbase vs Trigger.dev](https://www.hooksbase.com/compare/trigger-dev): Trigger.dev runs long-running durable tasks as your own code; Hooksbase runs the event path that feeds them. Where each fits, and what Trigger.dev does that Hooksbase does not.
- [Inbound email services compared](https://www.hooksbase.com/compare/inbound-email): CloudMailin, SendGrid Inbound Parse, Postmark inbound, and Mailgun Routes compared against Hooksbase email ingest — they parse the mail and hand you one HTTP POST; the difference is what happens if that POST fails.
- [Cron and scheduling services compared](https://www.hooksbase.com/compare/cron-services): cron-job.org, EasyCron, and Cronitor compared against Hooksbase scheduled webhooks — calling a URL on a cadence versus a scheduled firing that is recorded, retried, replayable, and lands in a dead-letter path.
- [Migrate from Hookdeck](https://www.hooksbase.com/guides/migrate-from-hookdeck): Concept-by-concept mapping from Hookdeck connections, sources, destinations, and filters onto Hooksbase equivalents.
- [Migrate from Svix](https://www.hooksbase.com/guides/migrate-from-svix): Concept-by-concept mapping from Svix applications, endpoints, and message types onto Hooksbase equivalents.

## Alternatives roundups

- [Alternatives index](https://www.hooksbase.com/alternatives): Roundups of the alternatives to each webhook and event infrastructure product, with Hooksbase listed as one option among several.
- [Hookdeck alternatives](https://www.hooksbase.com/alternatives/hookdeck): The strongest Hookdeck alternatives are Hooksbase when you need ingest beyond HTTP or your consumer is an AI agent, Svix when you are sending webhooks to your own customers and need enterprise compliance, Convoy when you want to self-host, and Hookdeck Outpost when you only need outbound delivery at a low cost per event.
- [Svix alternatives](https://www.hooksbase.com/alternatives/svix): The strongest Svix alternatives are Hookdeck Outpost when you want open-source outbound delivery at a low cost per event, Convoy when you want to self-host, and Hooksbase when your problem is ingest and delivery for an AI agent rather than sending webhooks to your customers — though Svix remains the better choice for outbound-only delivery needing SOC 2, HIPAA, or PCI-DSS.
- [QStash alternatives](https://www.hooksbase.com/alternatives/qstash): The strongest QStash alternatives are Hooksbase when you need signature verification on ingest, payload persistence, and replay rather than a queue that posts to URLs, Inngest or Trigger.dev when the real requirement is durable multi-step execution, and Zeplo when you want the smallest possible retry layer — though QStash remains the better fit when you need topic fan-out.
- [Inngest alternatives](https://www.hooksbase.com/alternatives/inngest): The closest Inngest alternative is Trigger.dev, which does the same durable execution job with managed compute and no timeout ceiling; QStash covers the simpler case of scheduled and retried HTTP calls; and Hooksbase solves the adjacent problem of getting events in reliably rather than executing them, which is why teams frequently run it alongside Inngest rather than instead of it.
- [Trigger.dev alternatives](https://www.hooksbase.com/alternatives/trigger-dev): The closest Trigger.dev alternative is Inngest, which does the same durable execution job but runs on compute you already operate; QStash covers simple scheduled and retried HTTP calls at a much lower price; and Hooksbase handles the separate problem of getting the event there reliably, which is why it is more often run in front of Trigger.dev than instead of it.
- [Convoy alternatives](https://www.hooksbase.com/alternatives/convoy): The strongest Convoy alternatives are Hookdeck Outpost when you want an open-source outbound build without the $999/mo tier gating transforms, Svix when compliance drives the decision, and Hooksbase or Hookdeck when you would rather not operate webhook infrastructure at all — Convoy remains the better choice if self-hosting is a requirement rather than a preference.

## Works with your stack

- [Hooksbase for OpenClaw](https://www.hooksbase.com/for-openclaw): Give your OpenClaw agent reliable triggers and durable outputs — no plumbing code.
- [Hooksbase for Hermes](https://www.hooksbase.com/for-hermes): Give your Hermes agent reliable triggers and durable outputs — no plumbing code.
- [Hooksbase for n8n](https://www.hooksbase.com/for-n8n): Give your n8n workflow reliable webhook ingest, replay, and DLQ — without leaving n8n.
- [Hooksbase for Make](https://www.hooksbase.com/for-make): Add reliable webhook ingest, replay, and DLQ in front of your Make scenarios — without leaving Make.
- [Hooksbase for Zapier](https://www.hooksbase.com/for-zapier): Give every Zap reliable webhook ingest, signature verification, and replay — for the events Zapier-by-Webhooks alone can’t cover.
- [Hooksbase for Pipedream](https://www.hooksbase.com/for-pipedream): Add reliable ingest, replay, and DLQ in front of your Pipedream workflows — including channels Pipedream HTTP triggers don’t cover.

## Provider integrations

- [Stripe webhooks](https://www.hooksbase.com/integrations/stripe): Verified Stripe webhooks for your AI agent.
- [GitHub webhooks](https://www.hooksbase.com/integrations/github): Verified GitHub webhooks for your AI agent.
- [Clerk webhooks](https://www.hooksbase.com/integrations/clerk): Verified Clerk webhooks for your AI agent.
- [Slack webhooks](https://www.hooksbase.com/integrations/slack): Verified Slack webhooks for your AI agent.
- [Resend webhooks](https://www.hooksbase.com/integrations/resend): Verified Resend webhooks for your AI agent.

## Reference

- [Documentation](https://www.hooksbase.com/docs): Full product documentation — quickstart, ingest, routing, Automations, replay, security, Public API reference, SDK and CLI.
- [Docs llms.txt](https://www.hooksbase.com/docs/llms.txt): Machine-readable index of the documentation with per-page markdown mirrors at /docs/*.md — start there for API and CLI detail.
- [Guides index](https://www.hooksbase.com/guides): Provider setup and integration guides.
- [Glossary index](https://www.hooksbase.com/glossary): Definitions for webhook and event-infrastructure terms.
- [Blog](https://www.hooksbase.com/blog): Architecture notes and background on event infrastructure for agents.

## Guides

- [Send inbound email to AWS SQS (no HTTP endpoint in the middle)](https://www.hooksbase.com/guides/email-to-sqs): Route an inbound email straight into SQS. Create an aws_sqs destination, point the webhook's email address at it, and every message lands as a durable entry.
- [Store form submissions in S3-compatible object storage](https://www.hooksbase.com/guides/form-submissions-to-object-storage): Send an HTML form submission, file uploads included, straight into an S3-compatible bucket. Create an object_storage destination and set a key prefix.
- [Replay an email-triggered event after your consumer was down](https://www.hooksbase.com/guides/replay-an-email-triggered-event): What happens to an inbound email when the destination is down, how retries and the dead-letter path work, and how to replay against the config that was live.
- [Lock down email ingest with sender allowlists](https://www.hooksbase.com/guides/sender-allowlists-for-email-ingest): Email ingest addresses are open by default. How sender allowlists work, the three pattern forms, and why blocked mail is dropped rather than bounced.
- [Run several scheduled jobs on one webhook with payload templates](https://www.hooksbase.com/guides/cron-triggered-agent-with-payload-templates): A payload template is what makes a cron firing mean something. Run several schedules on one webhook, tell them apart downstream, and route each separately.
- [Automate AI agent events before they reach the agent](https://www.hooksbase.com/guides/automate-ai-agent-events): Use Hooksbase Automations and Code Mode transforms to normalize, redact, test, and replay agent-facing events from a persisted dispatch snapshot.
- [AI agent examples (with the event triggers behind them)](https://www.hooksbase.com/guides/ai-agent-examples): Real AI agent examples by domain — support, revenue, engineering, ops, product — with the event triggers and event-layer features that make each one work.
- [How to receive Twilio webhooks (SMS, voice, status callbacks)](https://www.hooksbase.com/guides/receive-twilio-webhooks): Receiving Twilio webhooks: signature verification, the form-urlencoded payload format, fallback URLs, and how to stay reliable when Twilio does not retry.
- [How to receive Clerk webhooks reliably (user events for AI agents)](https://www.hooksbase.com/guides/receive-clerk-webhooks): Receiving Clerk webhooks: Standard Webhooks signature verification, event types, and how to plug user lifecycle events into your AI agents reliably.
- [How to receive Notion webhooks (page, database, and comment events)](https://www.hooksbase.com/guides/receive-notion-webhooks): Receiving Notion webhooks: the verification-token handshake, HMAC-SHA256 signature verification, common event types, and how to make ingest reliable.
- [How to receive Plaid webhooks reliably (transactions, items, errors)](https://www.hooksbase.com/guides/receive-plaid-webhooks): A complete guide to receiving Plaid webhooks: JWT-based signature verification with rotating keys, common webhook codes, and how to make ingest reliable.
- [How to receive Jira webhooks (issue, comment, and worklog events)](https://www.hooksbase.com/guides/receive-jira-webhooks): A complete guide to receiving Jira webhooks: the two flavors (admin-configured and Connect app), security gaps, JQL filtering, and how to make ingest reliable.
- [How to receive Resend webhooks reliably (email lifecycle events)](https://www.hooksbase.com/guides/receive-resend-webhooks): Receiving Resend webhooks: Standard Webhooks signature verification, email lifecycle event types, and how to pipe delivery telemetry to your agents.
- [How to receive Polar webhooks reliably (subscriptions, orders, customers)](https://www.hooksbase.com/guides/receive-polar-webhooks): Receiving Polar webhooks: Standard Webhooks signature verification, subscription and order event types, and how to make ingest reliable for billing flows.
- [How to receive Typeform submissions as webhooks (form responses)](https://www.hooksbase.com/guides/receive-typeform-webhooks): A complete guide to receiving Typeform submission webhooks: HMAC-SHA256 signature verification, the form_response payload shape, and how to make ingest reliable.
- [How to receive Mailchimp webhooks reliably (subscribe, unsubscribe, campaign events)](https://www.hooksbase.com/guides/receive-mailchimp-webhooks): Receiving Mailchimp webhooks: the URL verification handshake, the form-urlencoded payload format, the missing signature scheme, and making ingest reliable.
- [How to receive Brevo webhooks reliably (transactional and marketing email events)](https://www.hooksbase.com/guides/receive-brevo-webhooks): Receiving Brevo (formerly Sendinblue) webhooks: transactional and marketing event types, the missing signature scheme, and how to make ingest reliable.
- [How to receive Braze webhooks reliably (campaigns, canvases, and message events)](https://www.hooksbase.com/guides/receive-braze-webhooks): Receiving Braze webhooks: how the campaign and Canvas webhook channel works, configuring auth headers, payload templating, and making ingest reliable.
- [How to receive Figma webhooks (file updates, comments, library publishes)](https://www.hooksbase.com/guides/receive-figma-webhooks): A complete guide to receiving Figma webhooks: the passcode-based authentication model, event types for file changes and comments, and how to make ingest reliable.
- [How to receive Zapier webhooks (and when to skip the Zap entirely)](https://www.hooksbase.com/guides/receive-zapier-webhooks): Receiving Zapier webhooks: how Webhooks by Zapier sends requests, configuring auth, the trade-offs of routing through Zapier, and when to go direct instead.
- [How to receive n8n webhooks reliably (workflow-driven event delivery)](https://www.hooksbase.com/guides/receive-n8n-webhooks): A complete guide to receiving n8n webhooks: how the HTTP Request node sends data, configuring auth, and the trade-offs of using n8n as a relay vs sending directly.
- [Email-to-webhook for AI agents (parse, route, deliver)](https://www.hooksbase.com/guides/email-to-webhook-for-ai-agents): Email-to-webhook turns inbound mail into a structured JSON event your agent can process — no MX records, parsers, or attachment handling to build yourself.
- [Form-to-webhook with file uploads (embeddable forms for AI agents)](https://www.hooksbase.com/guides/form-to-webhook-with-file-uploads): Form-to-webhook turns any HTML form into a reliable agent trigger — multipart file uploads, CORS for embedded forms, and transforms to flatten the payload.
- [How to build an AI agent (with reliable event triggers)](https://www.hooksbase.com/guides/how-to-build-an-ai-agent): Step-by-step guide to building a production-ready AI agent: pick the model, define tools, set up reliable event triggers, handle retries, and ship.
- [How to receive Stripe webhooks reliably (signing, retries, replay)](https://www.hooksbase.com/guides/receive-stripe-webhooks): A complete guide to receiving Stripe webhooks in production: signature verification, retry handling, idempotency, replay, and the failure modes most teams hit.
- [How to receive GitHub webhooks reliably (events, secrets, payloads)](https://www.hooksbase.com/guides/receive-github-webhooks): A complete guide to receiving GitHub webhooks: event types, signature verification, retry semantics, common payload shapes, and how to make ingest reliable.
- [Slack webhooks: how to receive events reliably (Events API + Incoming Webhooks)](https://www.hooksbase.com/guides/receive-slack-events): Slack has two webhook patterns: Incoming Webhooks going out, and the Events API coming in. How each works, how to verify them, and how to make ingest reliable.
- [Discord webhooks: how they work and how to forward events into Discord reliably](https://www.hooksbase.com/guides/receive-discord-webhooks): Discord webhooks are outbound by default — your app POSTs to a channel URL. How they work, how to use them at scale, and how Discord's Interactions side works.
- [How to receive Shopify webhooks reliably (orders, products, customers)](https://www.hooksbase.com/guides/receive-shopify-webhooks): A complete guide to receiving Shopify webhooks: topic subscription, HMAC verification, retry semantics, and how to make ingest reliable for your store.
- [Ship your first agent event workflow](https://www.hooksbase.com/guides/ship-your-first-webhook-relay): Create a Hooksbase project, add a webhook, trigger your agent with a test event, and inspect the first delivery.
- [Verify provider webhooks before they reach your agent](https://www.hooksbase.com/guides/verify-provider-webhooks): Configure provider-aware inbound for Stripe, GitHub, Clerk, Slack, and Resend so only signed, trusted events fire your agent.
- [Stream agent event lifecycle to your observability stack](https://www.hooksbase.com/guides/send-delivery-events-to-observability): Event drains pipe delivery lifecycle events to HTTP, Axiom, Datadog, S3-compatible storage, or OTLP — so failures surface in the dashboards you already watch.
- [Connect Pipedream to Hooksbase](https://www.hooksbase.com/guides/connect-pipedream): Put Hooksbase in front of your Pipedream workflows for verified events, multi-channel ingest, replay, and DLQ — alongside your Pipedream code.
- [Use workflow blueprints to ship an agent in minutes](https://www.hooksbase.com/guides/agent-workflow-blueprints): Start from guided Hooksbase workflow blueprints for agent runtimes over HTTP, email, forms, schedules, queues, and object storage.
- [Connect Zapier to Hooksbase](https://www.hooksbase.com/guides/connect-zapier): Put Hooksbase in front of your Zaps for verified events, multi-channel ingest, replay, and DLQ — beyond what Webhooks-by-Zapier can do alone.
- [Connect Make to Hooksbase](https://www.hooksbase.com/guides/connect-make): Put Hooksbase in front of your Make scenarios for verified events, multi-channel ingest, replay, and DLQ — without changing your Make setup.
- [Connect n8n to Hooksbase](https://www.hooksbase.com/guides/connect-n8n): Put Hooksbase in front of your n8n workflow for verified events, multi-channel ingest, replay, and DLQ — without changing your n8n setup.
- [Connect Hermes to Hooksbase](https://www.hooksbase.com/guides/connect-hermes): Put Hooksbase in front of your Hermes agent for verified events, reliable delivery, replay, and observability.
- [Migrate from Hookdeck to Hooksbase](https://www.hooksbase.com/guides/migrate-from-hookdeck): Field-by-field mapping and switchover plan for moving from Hookdeck to Hooksbase — including connection translation, transformation mapping, and cutover.
- [Migrate from Svix to Hooksbase](https://www.hooksbase.com/guides/migrate-from-svix): Field-by-field mapping and switchover plan for moving from Svix to Hooksbase — including signature translation, routing re-implementation, and dual-run cutover.
- [Connect OpenClaw to Hooksbase](https://www.hooksbase.com/guides/connect-openclaw): Put Hooksbase in front of your OpenClaw agent for verified events, reliable delivery, replay, and observability.
- [Recover failed agent events with DLQ and replay](https://www.hooksbase.com/guides/recover-failed-agent-events): Walkthrough: inspect the DLQ, replay a single delivery, and bulk re-drive after fixing the agent — with deterministic dispatch snapshots.
- [Route events to the right agent with routing rules](https://www.hooksbase.com/guides/route-events-to-the-right-agent): Define multiple named destinations per webhook and priority-ordered rules matching on payload, headers, content type, or verified provider fields.
- [Schedule recurring agent runs with cron](https://www.hooksbase.com/guides/schedule-recurring-agent-runs): Configure per-webhook cron schedules to wake your agent on a cadence — daily summaries, hourly checks, periodic catch-up runs.

## Glossary

- [Attempt](https://www.hooksbase.com/glossary/attempt): One HTTP request within a delivery's retry chain.
- [Automation](https://www.hooksbase.com/glossary/automation): Versioned event-path logic that runs before a delivery reaches the destination.
- [Bulk replay (re-drive)](https://www.hooksbase.com/glossary/bulk-replay): Replaying or DLQ-re-driving many deliveries from a selection in one operation.
- [Code Mode](https://www.hooksbase.com/glossary/code-mode): The JavaScript transform mode inside Hooksbase Automations.
- [Cron expression](https://www.hooksbase.com/glossary/cron-expression): The five-field UTC schedule string that determines when a scheduled webhook fires.
- [Default destination](https://www.hooksbase.com/glossary/default-destination): Fallback destination for events no routing rule matches.
- [Delivery](https://www.hooksbase.com/glossary/delivery): A single dispatch lifecycle to a destination — includes all retry attempts.
- [Destination](https://www.hooksbase.com/glossary/destination): A target URL or typed sink within a webhook; a webhook can have many.
- [Dispatch snapshot](https://www.hooksbase.com/glossary/dispatch-snapshot): The transformed payload at the moment of dispatch, persisted so replays remain correct under config change.
- [DLQ (Dead-Letter Queue)](https://www.hooksbase.com/glossary/dlq): A holding area for messages that failed terminally so they can be inspected and recovered.
- [Email ingest](https://www.hooksbase.com/glossary/email-ingest): Accepting an inbound email as an event by sending it to a webhook’s generated ingest address.
- [Event drain](https://www.hooksbase.com/glossary/event-drain): A streamed feed of webhook lifecycle events to an external observability sink.
- [Exponential backoff](https://www.hooksbase.com/glossary/exponential-backoff): A retry schedule where each retry waits exponentially longer than the previous one.
- [Fan-out](https://www.hooksbase.com/glossary/fan-out): Delivering one event to multiple consumers in parallel.
- [Form ingest](https://www.hooksbase.com/glossary/form-ingest): Accepting a browser-posted HTML form submission as an event, including multipart file uploads.
- [HMAC](https://www.hooksbase.com/glossary/hmac): Hash-based Message Authentication Code — proves a message came from someone who knows a shared secret and was not modified.
- [Idempotency](https://www.hooksbase.com/glossary/idempotency): A property where performing an operation multiple times produces the same result as performing it once.
- [Inbound email parsing](https://www.hooksbase.com/glossary/inbound-email-parsing): Converting a raw RFC-822 message into structured fields a consumer can read.
- [Ingest](https://www.hooksbase.com/glossary/ingest): Accepting an event into Hooksbase via HTTP, email, form, or scheduled cron.
- [Ingest channel](https://www.hooksbase.com/glossary/ingest-channel): One of the four ways an event enters Hooksbase: HTTP, email, form, or scheduled cron.
- [Observability](https://www.hooksbase.com/glossary/observability): Knowing what arrived, what was attempted, what succeeded, and what failed — without grepping logs.
- [Overage](https://www.hooksbase.com/glossary/overage): Metered deliveries past the monthly included quota — paid tiers can opt in; free tier is hard-blocked.
- [Payload](https://www.hooksbase.com/glossary/payload): The body of an HTTP request — for webhooks, almost always JSON.
- [Payload template](https://www.hooksbase.com/glossary/payload-template): The optional static JSON object a scheduled webhook sends as its request body on each firing.
- [Payload transform](https://www.hooksbase.com/glossary/payload-transform): Per-webhook JSONPath extraction or Handlebars JSON template applied before dispatch.
- [Provider pack](https://www.hooksbase.com/glossary/provider-pack): Preconfigured inbound verification for a known provider — Stripe, GitHub, Clerk, Slack, or Resend.
- [Replay](https://www.hooksbase.com/glossary/replay): Re-running a retained event with the same input — typically after fixing a bug that caused the original to fail.
- [Retry](https://www.hooksbase.com/glossary/retry): Re-attempting a failed delivery on a backoff schedule until it succeeds or hits a retry budget.
- [Routing rule](https://www.hooksbase.com/glossary/routing-rule): A priority-ordered condition that selects which destination handles an event.
- [Scheduled ingest](https://www.hooksbase.com/glossary/scheduled-ingest): Firing a webhook on a recurring cron cadence with no external producer.
- [Sender allowlist](https://www.hooksbase.com/glossary/sender-allowlist): A per-webhook list controlling which email senders are permitted to trigger email ingest.
- [Standard Webhooks](https://www.hooksbase.com/glossary/standard-webhooks): An open spec for webhook signing headers that several modern providers (and Hooksbase) follow.
- [Strict FIFO](https://www.hooksbase.com/glossary/strict-fifo): Per-webhook ordering mode where the head delivery blocks subsequent ones until it succeeds or terminally fails.
- [Webhook](https://www.hooksbase.com/glossary/webhook): An HTTP request one service sends to another to notify it that something happened.
- [Workflow blueprint](https://www.hooksbase.com/glossary/workflow-blueprint): A dashboard-curated starting template for a first-workflow path.

## Blog

- [AI agent vs AI workflow: what is the difference?](https://www.hooksbase.com/blog/ai-agent-vs-ai-workflow): An AI workflow is a fixed sequence the model fills in; an AI agent picks the path itself. The difference, when each fits, and the hybrid that ships.
- [AI workflow automation: a practical guide](https://www.hooksbase.com/blog/ai-workflow-automation): AI workflow automation combines LLMs with deterministic steps to handle repetitive work. How to design and ship one, including the event layer under it.
- [Event-driven architecture for AI agents (a practical primer)](https://www.hooksbase.com/blog/event-driven-architecture-for-ai-agents): Event-driven architecture decouples producers from consumers. What it is, why AI agents need it more than classical software, and the patterns that work.
- [Event sourcing in plain English (for engineers shipping agents)](https://www.hooksbase.com/blog/event-sourcing-in-plain-english): Event sourcing stores every change as an immutable event and rebuilds state by replaying them. What it is, when it fits, and how it relates to agent replay.
- [What is a message queue? (and when webhooks are a better fit)](https://www.hooksbase.com/blog/what-is-a-message-queue): A message queue is a durable buffer between producers and consumers. How queues work, when to use one, and when webhooks are the better tool instead.
- [What is SQS? A practical primer for forwarders](https://www.hooksbase.com/blog/what-is-sqs): Amazon SQS is a managed message queue. What it is, how Standard and FIFO queues differ, when SQS is the right tool, and how webhook events get into it.
- [What is EventBridge? AWS's pub/sub event bus explained](https://www.hooksbase.com/blog/what-is-eventbridge): Amazon EventBridge is AWS's event bus, routing events from many sources to many targets by rule. What it is, when it fits, and how webhook events get onto it.
- [Kafka vs SQS for webhook fan-out: when each fits](https://www.hooksbase.com/blog/kafka-vs-sqs): Kafka and SQS solve overlapping problems differently. When each fits for fanning webhook events out to many consumers — and the third option to try first.
- [Webhook DLQs: design and recovery patterns](https://www.hooksbase.com/blog/webhook-dlqs): A dead-letter queue holds messages that failed terminally so you can inspect and recover them. How DLQs work, how to design one, and the recovery patterns.
- [Observability for webhook delivery (events, drains, alerts)](https://www.hooksbase.com/blog/observability-for-webhook-delivery): Know what arrived, what was attempted, what succeeded, and what failed — without grepping logs. What to instrument for webhook delivery, and where to send it.
- [Building webhook infrastructure on Cloudflare Workers](https://www.hooksbase.com/blog/webhook-infrastructure-on-cloudflare-workers): What we learned building Hooksbase on Cloudflare Workers: no cold starts, D1, R2, Durable Objects — the wins, the constraints, and when not to use them.
- [Durable Objects for per-tenant webhook state](https://www.hooksbase.com/blog/durable-objects-for-webhook-state): Cloudflare Durable Objects are single-instance actors with strongly-consistent storage. When they fit webhook state, three production patterns, and when not to.
- [What is agentic AI? Definition, examples, and how it works](https://www.hooksbase.com/blog/what-is-agentic-ai): Agentic AI is software that perceives, decides, and acts on its own, without a human prompting each step. Examples, and the event layer that keeps it reliable.
- [What is an AI agent? A practical definition for builders](https://www.hooksbase.com/blog/what-is-an-ai-agent): An AI agent is an LLM-driven program taking goal-directed actions in a loop. Components, types, and the event layer that keeps one reliable in production.
- [AI agent platforms compared — and the event layer they all skip](https://www.hooksbase.com/blog/ai-agent-platforms-compared): A practical look at the AI agent platform landscape: what each does well, where they fall short, and the event-infrastructure gap every team eventually hits.
- [What is a webhook? Complete guide with examples](https://www.hooksbase.com/blog/what-is-a-webhook): A webhook is an HTTP request one service makes to notify another that something happened. Examples, payload format, security, and using them in production.
- [Webhooks vs APIs: when to use each (and when to use both)](https://www.hooksbase.com/blog/webhooks-vs-apis): A webhook is push-based, an API is pull-based. Here is when to use each, when to use both, and the failure modes that decide it.
- [Webhook URLs explained: structure, examples, security](https://www.hooksbase.com/blog/webhook-urls-explained): A webhook URL is the HTTPS endpoint a service POSTs to when an event happens. Structure, examples, security, and how to design one that survives production.
- [JSON payloads explained (and why webhooks use them)](https://www.hooksbase.com/blog/what-is-a-payload): A payload is the body of an HTTP request — what the sender wants the receiver to act on. What payloads look like, and what production systems do with them.
- [Webhook testing: how to test webhooks locally, in CI, and in production](https://www.hooksbase.com/blog/webhook-testing-guide): A complete guide to testing webhooks at every stage: local development with tunneling, CI with fixtures and replay, and production with delivery history and replay.
- [The complete guide to idempotency keys (for webhooks and APIs)](https://www.hooksbase.com/blog/idempotency-keys): An idempotency key makes a request safe to retry without duplicating the result. How they work, how to implement them, and the failure modes that need one.
- [Your agent shouldn't only listen to HTTP](https://www.hooksbase.com/blog/email-and-form-ingest): Email, forms, and scheduled triggers as first-class event sources for AI agents. One delivery pipeline, four ingest channels.
- [Why automation platforms need an event layer in front](https://www.hooksbase.com/blog/automation-platforms-need-event-infrastructure): n8n, Make, Zapier, and Pipedream are great workflow runtimes. None ships production-grade event infrastructure — here is what that gap looks like.
- [Routing, transforms, and replay for AI agents](https://www.hooksbase.com/blog/routing-transforms-and-replay): Hooksbase keeps source payloads, dispatch snapshots, routing decisions, and replay lineage together — so your agent recovers even when configurations drift.
- [Migrating from classical webhook delivery to agent event infrastructure](https://www.hooksbase.com/blog/migrating-webhook-stack-to-agent-infra): What changes when the consumer of your webhooks is an AI agent instead of a SaaS endpoint — and how to migrate from Svix, Hookdeck, or a DIY setup.
- [Why no-code agent platforms need real event infrastructure](https://www.hooksbase.com/blog/no-code-agents-need-real-event-infra): OpenClaw and similar no-code agent tools give you a builder — but not the event layer. Here is what separates a demo from a production agent.
- [The agent production readiness checklist](https://www.hooksbase.com/blog/agent-production-checklist): What you need on the event layer before putting an AI agent in front of real users — quotas, strict FIFO, throttling, DLQ, alerts, audit logs.
- [Verify Stripe, GitHub, Clerk, Slack, and Resend before they reach your agent](https://www.hooksbase.com/blog/verified-providers-for-agents): Why signature verification matters more when an AI agent is the consumer — and how configured provider packs keep it out of your agent code.
- [Deterministic replay is non-negotiable for agents](https://www.hooksbase.com/blog/deterministic-replay-for-agents): Why AI agents need deterministic replay more than classical SaaS does — and how Hooksbase's dispatch snapshots make it work even when configs change.
- [Every way your agent can get triggered](https://www.hooksbase.com/blog/agent-triggers-beyond-http): HTTP, email, forms, and scheduled cron as first-class agent triggers — what each channel is good for and when to reach for it.
- [Event infrastructure for AI agents](https://www.hooksbase.com/blog/event-infrastructure-for-ai-agents): Why every AI agent needs an event layer — and why building it from scratch costs more than the agent itself.

## Owned profiles

- [GitHub](https://github.com/hooksbase): SDK, CLI, and example repositories.
- [npm @hooksbase/sdk](https://www.npmjs.com/package/@hooksbase/sdk): TypeScript SDK.
- [npm @hooksbase/cli](https://www.npmjs.com/package/@hooksbase/cli): command-line client.
- [Dashboard](https://app.hooksbase.com): the authenticated product surface.