Niches · Event delivery & webhooks
Call an endpoint on a schedule
One company's docs show a full fit.
What counts as done
The endpoint is called at each scheduled time with a signed request, each run and its response status is readable afterwards, and a missed or failed run is retried or reported.
Measured, for our own tests: start within 60 seconds of the scheduled minute. No docs we read state these figures, so they don't count against a listing here.
How agents ask for it: run this every night at 2
, call my agent every hour
, replace this cron job
, send a heartbeat every five minutes
Does the job 1
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| Upstash QStash BB Upstash, Inc. | Schedules take cron with a CRON_TZ time zone, each delivery is JWT-signed, /v2/logs records each attempt with responseStatus, and failed runs retry then land in the DLQ. source |
Does the job, with a limit 3
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| 402cron B Georgi Kalchev (operator, a named person; no company named) | Signed HMAC deliveries on 5-field UTC cron, retried at 60 and 120 seconds on timeout or unreachable, and a pause notice is sent; but no endpoint returns each run and its status, only counters and the last run. source |
| Amazon EventBridge BB Amazon Web Services, Inc. | Scheduler fires with 60-second precision in a chosen time zone, retries by policy and sends failures to a dead-letter queue, but HTTP targets go through unsigned API destinations and no API lists each run with its status. acc-16 moved late cron jobs here. source |
| Webhook Relay C AppScension Ltd | Recurring cron webhooks exist, but the guide sets them up in the dashboard and shows runs there; no API, time-zone or signing detail for scheduled calls was in the pages read. source |
Doesn't do this job 8
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Ably BB Ably Realtime Ltd | No scheduler. source |
| Centrifugo C Centrifugal Labs LTD | No scheduler. source |
| Convoy C Frain Technologies Inc. | No scheduler. source |
| Hook0 B FGRibreau SARL | No scheduler. source |
| Hookdeck A Hookdeck Technologies Inc. | No cron or scheduled calls; only retries can be scheduled. source |
| PubNub BB PubNub Inc. | No scheduler. source |
| Pusher Channels D MessageBird UK Limited | No scheduler. source |
| Svix BB Svix Inc. | No scheduler. source |
What stops agents finishing
- schedule service needs a person to sign up or add a card
- run skipped while the previous one is still in flight with no notice
- UTC-only cron where the task needs local time
Around it
Before: infrastructure.deploy-app. After: observability.scheduled-watch.
Where this comes from
Weight 11 of 100 in Event delivery & webhooks: 5 of 40 accounts; two are agent harness descriptions (acc-12, acc-15) rather than reports of a listing
The same as data: /api/v1/use-cases/webhooks.schedule-call.json, or the MCP tool get_use_case with id webhooks.schedule-call. Other jobs in this category: /api/v1/niches?category=webhooks.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.