Webhook and event-infrastructure terms, defined.

Hash-based Message Authentication Code — proves a message came from someone who knows a shared secret and was not modified.

The body of an HTTP request — for webhooks, almost always JSON.

An open spec for webhook signing headers that several modern providers (and Hooksbase) follow.

An HTTP request one service sends to another to notify it that something happened.

A holding area for messages that failed terminally so they can be inspected and recovered.

A retry schedule where each retry waits exponentially longer than the previous one.

A property where performing an operation multiple times produces the same result as performing it once.

Re-running a retained event with the same input — typically after fixing a bug that caused the original to fail.

Re-attempting a failed delivery on a backoff schedule until it succeeds or hits a retry budget.

A per-webhook list controlling which email senders are permitted to trigger email ingest.

Per-webhook ordering mode where the head delivery blocks subsequent ones until it succeeds or terminally fails.

Delivering one event to multiple consumers in parallel.

Converting a raw RFC-822 message into structured fields a consumer can read.

One of the four ways an event enters Hooksbase: HTTP, email, form, or scheduled cron.

Knowing what arrived, what was attempted, what succeeded, and what failed — without grepping logs.

One HTTP request within a delivery's retry chain.

Versioned event-path logic that runs before a delivery reaches the destination.

Replaying or DLQ-re-driving many deliveries from a selection in one operation.

The JavaScript transform mode inside Hooksbase Automations.

The five-field UTC schedule string that determines when a scheduled webhook fires.

Fallback destination for events no routing rule matches.

A single dispatch lifecycle to a destination — includes all retry attempts.

A target URL or typed sink within a webhook; a webhook can have many.

The transformed payload at the moment of dispatch, persisted so replays remain correct under config change.

Accepting an inbound email as an event by sending it to a webhook’s generated ingest address.

A streamed feed of webhook lifecycle events to an external observability sink.

Accepting a browser-posted HTML form submission as an event, including multipart file uploads.

Accepting an event into Hooksbase via HTTP, email, form, or scheduled cron.

Metered deliveries past the monthly included quota — paid tiers can opt in; free tier is hard-blocked.

The optional static JSON object a scheduled webhook sends as its request body on each firing.

Per-webhook JSONPath extraction or Handlebars JSON template applied before dispatch.

Preconfigured inbound verification for a known provider — Stripe, GitHub, Clerk, Slack, or Resend.

A priority-ordered condition that selects which destination handles an event.

Firing a webhook on a recurring cron cadence with no external producer.

A dashboard-curated starting template for a first-workflow path.