A cron expression is the schedule string attached to a webhook that determines when scheduled ingest fires. Hooksbase uses the standard five-field format:
* * * * *
minute hour day-of-month month day-of-week
(0-59) (0-23) (1-31) (1-12) (0-6)
Examples: 0 * * * * fires hourly on the hour, */15 * * * * every fifteen minutes, and 0 3 * * 1 at 03:00 on Mondays.
Always UTC
Expressions are evaluated in UTC. There is no per-schedule timezone and no daylight-saving adjustment, so convert your intended local time before writing the expression. A job meant for 09:00 in a summer-time zone will drift by an hour relative to local clocks twice a year unless you account for it.
What the schedule tracks
Alongside the expression, each schedule stores an optional name, an optional payload template, a status of active or paused, and the lastFiredAt and nextFireAt timestamps in Unix milliseconds — which is the fastest way to confirm a schedule is actually live.
Related terms
- Scheduled ingest
Firing a webhook on a recurring cron cadence with no external producer.
Read - Payload template
The optional static JSON object a scheduled webhook sends as its request body on each firing.
Read - Ingest channel
One of the four ways an event enters Hooksbase: HTTP, email, form, or scheduled cron.
Read - Attempt
One HTTP request within a delivery's retry chain.
Read