What is scheduled ingest?
Scheduled ingest is the channel where Hooksbase itself produces the event. Instead of waiting for an external producer, a cron expression attached to a webhook fires it on a cadence.
Scheduled webhooks require Starter or above.
The schedule model
A schedule belongs to one webhook and stores a standard five-field cron expression evaluated in UTC, an optional name, an optional payload template, a status of active or paused, and the lastFiredAt and nextFireAt timestamps in Unix milliseconds. Schedules are managed from the dashboard or through /v1/webhooks/{id}/schedules.
Without a template, a firing sends a default body carrying source set to scheduled, plus scheduleId, webhookId, cronExpression, and firedAt. A template replaces that body rather than extending it.
Recurring, not one-off
Schedules express a repeating cadence. For a single event that should land at one specific future moment, use delayed delivery instead — the x-hooksbase-deliver-at header on ingest, or a webhook-level default delay, both accepting times up to a year out. Delayed delivery requires Pro or above, and webhooks configured for strict FIFO reject future scheduling.
A firing is an ordinary delivery
Schedules are independent of public ingest but create deliveries through the same engine. The webhook's destination, routing rules, transforms, retry policy, analytics, replay, and DLQ all apply. A scheduled run that fails is retried and lands in the dead-letter path rather than disappearing.
See Scheduled webhooks for the full channel overview.
Frequently asked questions
What does a scheduled firing send if there is no payload template?
A default body carrying source set to scheduled, plus scheduleId, webhookId, cronExpression and firedAt. Setting a template replaces that body rather than extending it.
What is the difference between a schedule and delayed delivery?
A schedule expresses a repeating cadence. For a single event that should land at one specific future moment, use delayed delivery instead — the x-hooksbase-deliver-at header on ingest or a webhook-level default delay, both accepting times up to a year out. Delayed delivery requires Pro or above, and webhooks configured for strict FIFO reject future scheduling.
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 - Cron expression
The five-field UTC schedule string that determines when a scheduled webhook fires.
Read - Payload template
The optional static JSON object a scheduled webhook sends as its request body on each firing.
Read - Sender allowlist
A per-webhook list controlling which email senders are permitted to trigger email ingest.
Read