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.