Blog · Webhooks

Webhook integrations and scheduled trigger patterns

Webhooks are the digital messengers between services. These posts cover how to trigger them on a real schedule with Crontap, plus the patterns for Make, Zapier, GitHub Actions and beyond.

About this topic

Webhooks

5 itemsBlog

Webhooks shine in one direction: when something happens here, tell something there. Cron is the opposite direction: when the clock says so, fire here. Pair them and you get cadence-driven workflows: every minute fire a Make webhook to push the latest Airtable rows into the warehouse; every 5 minutes ping a Zapier catch hook to fan out a notification; every hour workflow_dispatch a GitHub Action because GitHub's own schedule event drifts by 15+ minutes under load.

Crontap fires the webhook on real cron syntax, per-IANA timezone, with custom headers and JSON payloads, retries on 5xx, and failure alerts to Slack, Discord, Telegram, email, or another webhook. The posts below cover the primer on webhooks themselves, the Make and Zapier integrations end-to-end, the every-minute pattern, and the GitHub Actions drift workaround.

Blog on Webhooks

5 items

Related on Crontap

The same Webhooks topic, from other angles.

FAQ

Common questions on Webhooks

Webhook vs cron job. What's the difference?
A webhook is an HTTP request fired from one service to another in response to an event. A cron job is an HTTP request fired on a schedule. Pair them: a Crontap schedule fires the webhook on the cadence you want, the receiving service does the work.
How is firing a Make webhook from Crontap different from Make's built-in schedule?
Make's schedule charges per-operation and floors at cadences that depend on the plan. Crontap fires the Make webhook on real cron syntax (per-IANA timezone, 1-minute floor on Pro), so the scenario runs on the cadence you actually need with one round-trip per fire.
GitHub Actions cron drifts. Can a webhook fix that?
Yes, by switching to workflow_dispatch. Crontap fires a POST to the workflow_dispatch API on time, and the workflow runs without GitHub's schedule-event throttling. The dedicated post walks the auth and the workflow YAML.
How do I secure the webhook endpoint?
A shared-secret header check on the receiving side. Crontap sends configurable custom headers per schedule, so a long random token in the schedule header and the same value in the receiver's env var keeps drive-by traffic out.

More from Crontap

Topics across the site.

Every topic Crontap covers, in one row. Each one has its own page on the blog 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

GET

/wp-cron.php?doing_wp_cron=1

Running
Your next schedule

Schedule

"every 5 minutes"

Next

in 23s