What is an ingest channel?
An ingest channel is a route by which an event enters Hooksbase. There are four, and a single webhook can use all of them at once.
| Channel | Producer | Credential | Availability |
|---|---|---|---|
| HTTP | Any service that can POST | Bearer ingest secret | All plans |
| A mailbox or a vendor that only sends mail | The generated ingest address | All plans; allowlist writes Starter+ | |
| Form | A browser posting an HTML form | The unguessable form URL | All plans |
| Scheduled | None — Hooksbase fires it | Configured on the webhook | Starter and above |
Why the distinction matters
Most event tooling speaks HTTP and nothing else, which pushes the other channels into separate services — a form backend here, an inbound email parser there, a cron service somewhere else. Each arrives with its own retry semantics, its own history, and its own failure modes.
In Hooksbase all four channels normalize to the same internal event shape, so a form submission and a Stripe webhook are the same kind of object downstream. Routing rules, Automations, retries, signing, delivery history, replay, and the DLQ work identically regardless of how the event arrived.
Identifying the channel downstream
The parsed payload records which channel produced the event — email-sourced events carry source set to email, for example — so a routing rule can match on it and send different channels to different destinations.
See Event sources for the full comparison.
Frequently asked questions
What are the four Hooksbase ingest channels?
HTTP, authenticated with the bearer ingest secret and available on all plans; email, through the webhook's generated address, on all plans with allowlist writes from Starter up; form, through the unguessable form URL, on all plans; and scheduled cron, which Hooksbase fires itself, on Starter and above.
Do the four channels behave differently downstream?
No. All four normalize to the same internal event shape, so a form submission and a Stripe webhook are the same kind of object. Routing rules, Automations, retries, signing, delivery history, replay and the DLQ work identically regardless of how the event arrived.
What is Hooksbase?
Hooksbase is event infrastructure for AI agents. It ingests events over four channels — HTTP, email, HTML 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. It is a hosted service, runs on Cloudflare Workers, is operated at hooksbase.com, and is not affiliated with — and shares no code or ownership with — other similarly named webhook, hook, or tunnelling tools.
Related terms
- Ingest
Accepting an event into Hooksbase via HTTP, email, form, or scheduled cron.
Read - Email ingest
Accepting an inbound email as an event by sending it to a webhook’s generated ingest address.
Read - Form ingest
Accepting a browser-posted HTML form submission as an event, including multipart file uploads.
Read - Observability
Knowing what arrived, what was attempted, what succeeded, and what failed — without grepping logs.
Read