WHAT IS A SCHEDULED WEBHOOK?
What is a scheduled webhook?
A scheduled webhook is an HTTP POST delivered to your endpoint on a recurring cron-defined schedule, carrying a signed event payload. Definition, how it works, and how it differs from cron.
A scheduled webhook is an HTTP POST that an external scheduler delivers to your endpoint on a recurring, time-based trigger — a cron expression, a simple interval, or a one-off time — carrying a signed, structured event payload. It turns any webhook receiver into a cron-driven job, without giving the receiver its own scheduler. Recurrence Cloud is a managed platform for exactly this.
How a scheduled webhook works
- Define the schedule. A cron expression (
0 6 * * *) plus a timezone, so “6am” means the right 6am. Managed by dashboard or created via API by your systems or agents. - Register the receiver. The HTTPS URL that deliveries should hit, with a signing secret.
- Define events. Named, structured payloads (
subject: the grouping key;payload: your data) attached to the schedule — a series of events sharing a subject is delivered as one batch. - The scheduler fires. At the scheduled time it assembles the events, signs the delivery, and POSTs it to your receiver with
Content-Type: application/json. - Your receiver does the work. Verify the signature, read the events, process them. Status codes, latency, and retries are recorded in an activity trail you can inspect.
{
"events": [
{ "id": "evt_01", "subject": "digest-prod", "scheduleName": "morning-digest", "data": { "window": "overnight" } }
],
"organizationId": "org_1",
"appId": "app_1",
"webhookId": "wh_1",
"batchId": "bat_01",
"attempt": 1,
"firedAt": "2025-11-23T11:00:00.500Z"
}
Scheduled webhook vs. cron job
| Classic cron | Scheduled webhook | |
|---|---|---|
| Runs | A command on a machine you operate | An HTTP call to an endpoint you own |
| Needs a host | Yes — a server that must not sleep | No — works with scale-to-zero and serverless |
| Payload | Whatever the command can read | Signed JSON events you defined |
| Security | OS-level trust | HMAC signature your receiver verifies |
| Observability | Syslog, exit codes | Per-delivery status, latency, retry, alerting |
| Changed via | Editing crontab + deploy | Dashboard or API, no deploy |
Cron is a fine clock. A scheduled webhook is the clock plus delivery, verification, batching-by-subject, retries, and an audit trail — and it works in environments where installing cron is impossible by design.
Scheduled webhook vs. delayed queue jobs
A queue with delay= schedules work you enqueue; a scheduled webhook schedules time itself. Queues fire “when this job reaches the front,” schedules fire “when the clock says so, whether or not anything is queued.” They compose: the webhook is the recurring trigger; the queue absorbs the fan-out.
Why the signature matters
Any endpoint that fires jobs must prove who is calling. Scheduled webhook platforms sign deliveries — Recurrence Cloud signs each request with HMAC-SHA256 over the raw body — and send identifying headers (X-Organization-Id, X-App-Id, X-Webhook-Id, X-Recurrence-Batch-Id, X-Recurrence-Attempt). Verify before you trust: an unsigned scheduled webhook that triggers work is a remote trigger anyone who finds the URL can fire. See verifying signed webhook requests.
Who uses scheduled webhooks
- SaaS teams — nightly per-tenant syncs and digests, batched by tenant
- Platform/DevOps — certificate sweeps, backup verification, health checks at fixed times
- Finance ops — month-end invoice runs and daily rollups as batched event series
- AI agent builders — MCP tool calls and agent tasks on a schedule (see scheduled MCP tool calls)
- Edge/serverless apps — any workload that can’t hold its own clock (see scheduling edge functions)
Where to go next
- How to schedule webhooks with cron — the full zero-to-first-delivery walkthrough
- Event-chain patterns — turning one delivery into a series of events
- Cron expression cheat sheet — copy-paste schedules for every cadence
FAQ
What is a scheduled webhook?
A scheduled webhook is an HTTP POST delivered to your endpoint on a recurring, time-based trigger — a cron expression, a simple interval, or a one-off time — carrying a signed, structured event payload. It turns any webhook receiver into a cron-driven job without giving it its own scheduler.
What is the difference between a scheduled webhook and a cron job?
A cron job runs a command on a machine you operate; a scheduled webhook makes an HTTP call to an endpoint you already own. Scheduled webhooks work in scale-to-zero and serverless environments where nothing can wake itself up, and they come from a managed platform with signing, retries, and a delivery audit trail.
How does a scheduled webhook work?
A managed scheduler evaluates your cron expression against a timezone, assembles the events you defined for that fire, signs the delivery with an HMAC secret, and POSTs it to your registered HTTPS endpoint. Your receiver verifies the signature, reads the events array, and does the work — the platform records status codes, latency, and retries.
Are scheduled webhooks secure?
They should be, and Recurrence Cloud makes it default: every delivery is signed with HMAC-SHA256 using a secret tied to your account, with organization, app, webhook, batch, and attempt headers. A receiver should reject any request whose signature does not verify — an unsigned scheduled webhook that triggers jobs is a remote trigger anyone can fire.
What can I use a scheduled webhook for?
Daily and weekly digest emails, nightly data syncs and ETL, month-end invoice runs, cache warming, certificate and backup checks, tenant sweep jobs, and recurring AI agent tasks such as MCP tool calls on a schedule.
How much does a scheduled webhook service cost?
Recurrence Cloud offers a free tier covering a handful of schedules, with paid plans for more schedules, longer retention, and higher delivery volumes — see the pricing page. Alternatives price per platform (Cloudflare/Vercel cron are free but platform-locked) or per execution (queue-based schedulers).