Email ingest is the channel that turns an inbound email message into a Hooksbase event. Every webhook is issued a permanent address of the form hook_xyz@ingest.hooksbase.com, and mail sent to that address becomes a delivery on the webhook.
There is no public HTTP route for email ingest — the producer simply sends mail. The address itself is the access credential, so rotate the webhook if it leaks.
What the parsed payload contains
Hooksbase parses the message rather than handing you raw MIME. The event carries source set to email, plus from, to, subject, the plain-text and HTML bodies, selected headers, messageId, date, and an attachments array. Attachment files are persisted on paid plans (15 MB per file, 50 MB per ingest) and referenced by a signed URL; free projects receive attachment metadata only.
Sender allowlists
Each webhook can carry a sender allowlist restricting who may trigger it. Until entries are added the channel is open — any sender who knows the address is accepted. Creating allowlist entries requires Starter or above.
Why it is not a separate pipeline
An email-sourced event is an ordinary delivery. The webhook's routing rules, Automations, retry policy, signing, delivery history, replay, and DLQ behave exactly as they would for an HTTP event. That is the point of treating email as a first-class ingest channel rather than a bolt-on.
See Email to webhook for the full channel overview.
Related terms
- Ingest
Accepting an event into Hooksbase via HTTP, email, form, or scheduled cron.
Read - Form ingest
Accepting a browser-posted HTML form submission as an event, including multipart file uploads.
Read - Scheduled ingest
Firing a webhook on a recurring cron cadence with no external producer.
Read - Sender allowlist
A per-webhook list controlling which email senders are permitted to trigger email ingest.
Read