Webhook Cron Job Alerts — Connect Any Tool
Send cron job failure, recovery, and circuit-breaker alerts to any HTTPS endpoint — your own service, Zapier, Make, n8n, Datadog, or anything else that speaks HTTP. Secure every delivery with HMAC-SHA256 request signing so your receiver can verify each payload is authentic.
Start freeHow Webhook alerts work
When a scheduled HTTP cron job or heartbeat monitor on CronJobPro fails — due to a non-2xx response, a timeout, a DNS or connection error after your configured retries — CronJobPro sends an HTTP POST with a JSON payload to your endpoint. The same webhook fires when the job recovers or is auto-disabled by the circuit breaker after repeated failures. If you configure a signing secret, each request includes an HMAC-SHA256 signature over the raw body so your receiver can reject spoofed payloads before acting on them.
Set up Webhook notifications
You'll need your Your HTTPS endpoint URL (e.g. https://yourdomain.com/hooks/cronjobpro).
- 1
Create or identify your HTTPS endpoint
Your endpoint must be publicly reachable over HTTPS and return a 2xx response within a reasonable timeout. It can be a custom service, a Zapier/Make/n8n webhook trigger URL, a Datadog Events intake URL, or any other HTTP listener.
- 2
Test your endpoint with the Webhook Tester
Before wiring up alerts, paste your URL into the CronJobPro Webhook Tester at /tools/webhook-tester. It sends a sample POST payload so you can confirm your endpoint receives and parses the JSON correctly.
- 3
Add a Webhook notification channel
Go to Settings → Notifications and create a new channel of type Webhook. Paste your HTTPS endpoint URL. Optionally enter a signing secret — CronJobPro will include an HMAC-SHA256 signature header on every request so your handler can verify authenticity.
- 4
Attach the channel to your jobs or monitors
Open any scheduled cron job or heartbeat monitor, go to its Notifications section, and select the Webhook channel you just created. You can attach the same channel to multiple jobs or use separate channels per service.
- 5
Configure an alert threshold if needed
To suppress noise from transient failures, set an alert threshold on the job. CronJobPro will withhold the alert until that number of consecutive failures is reached, then POST to your endpoint.
- 6
Verify HMAC signatures in your receiver
If you set a signing secret, compute HMAC-SHA256 over the raw request body using your secret and compare it to the signature header CronJobPro sends. Reject any request where the signatures do not match.
Frequently asked questions
What events trigger a webhook POST?
CronJobPro sends a POST to your endpoint when a job or heartbeat monitor fails (non-2xx response, timeout, or connection/DNS error after configured retries), when it recovers after a failure, or when the circuit breaker auto-disables the job after repeated failures.
How do I verify that a request actually came from CronJobPro?
Set a signing secret on your Webhook channel. CronJobPro computes HMAC-SHA256 over the raw request body using that secret and includes the result in a signature header. In your receiver, perform the same computation and compare — reject requests where the signatures do not match.
Can I use this with Zapier, Make, or n8n?
Yes. Each of those platforms exposes a webhook trigger URL that accepts an HTTP POST. Paste that URL as your endpoint in the CronJobPro Webhook channel. From there you can route alert data to Slack, PagerDuty, a spreadsheet, or any other app those platforms support.
How can I test my endpoint before attaching it to a live job?
Use the CronJobPro Webhook Tester at /tools/webhook-tester. Paste your endpoint URL and it will send a sample JSON payload so you can inspect headers, verify signature handling, and confirm your receiver responds correctly — all without waiting for a real failure.
Other integrations
Monitor your cron jobs in Webhook
Schedule HTTP jobs and heartbeat monitors, then get failure and recovery alerts where your team already works.