Use cases · Webhooks
Webhook cron jobs and scheduled HTTP triggers
Most spokes here are technically webhook patterns. This page is the explicit one: any URL, any cadence, any payload, on a real cron.
About this topic
Webhooks
Almost every spoke on this site is, mechanically, a scheduled HTTP call. This category is the explicit, generic version: you have a webhook URL (a Discord channel webhook, a custom Lambda, a Bubble API endpoint, a third-party intake form, anything that accepts HTTPS), and you want it called on a clock. No platform-specific gotchas, no plan-gated cadence, no UTC-only constraints.
Crontap's core feature surface is exactly this. Pick a URL, pick a cron expression (or describe it in plain English), pick a timezone, optionally attach custom headers and a JSON body, and the schedule starts firing. Run logs capture the response code and duration; failure alerts route to Slack, Discord, Telegram, email or another webhook. The discord-webhooks spoke is a concrete example of the pattern in the messaging cluster; for everything else, this category is the catch-all.
Use cases on Webhooks
1 itemRelated on Crontap
The same Webhooks topic, from other angles.
FAQ
Common questions on Webhooks
- What's the difference between a webhook and a scheduled HTTP call?
- Webhook is a label for an HTTP endpoint that accepts inbound calls and does something. A scheduled HTTP call is the act of firing one on a clock. Crontap is the scheduler; whatever endpoint you point it at is your webhook. Same wire protocol, different vocabulary.
- Can I send a custom JSON body on every fire?
- Yes. Each schedule has a request method (GET, POST, PUT, etc.), optional headers, and an optional body (JSON, form-urlencoded, plain text). The same body is sent on every fire of that schedule. For payloads that need to vary per fire, your endpoint can read query parameters (e.g. ?date=today) or compute the variation server-side.
- How do I secure a public webhook from being hit by anyone?
- Add a custom header on the Crontap schedule (X-Crontap-Token: <secret>) and check it inside your endpoint. Reject requests without the header. The secret never leaves Crontap and your server. Alternatively, sign the request body with HMAC and verify on the receiver.
More from Crontap
Topics across the site.
Every topic Crontap covers, in one row. Each one has its own page on the use cases surface.
Ready to fix it?
Point Crontap at any URL. Pick any cron. Done.
WordPress, Shopify, Railway, Cloud Run, Vercel, HubSpot, Ghost, your own box. If it answers HTTP, Crontap can drive it on a clock you can read, in the timezone that actually matters, and page you when something breaks.
Free forever tier ・ No credit card required
/wp-cron.php?doing_wp_cron=1
Schedule
"every 5 minutes"
Next
in 23s