schedule Cron

Know the moment a cron job fails

Push notifications and a centralized timeline for every cron job. Get alerted the second a scheduled task fails, search past runs, forward failures to Discord or Slack.

Start free See pricing

error

The problem

A cron throws an error in the middle of the night. The shell mails root, root forwards nowhere, and you only find out two days later when the backup is missing. Side projects don't justify a full monitoring stack just to catch this.

check_circle

How Alarum solves it

Each cron POSTs success or failure to Alarum at the end of its run. Failures push to your phone, successes go quietly to the inbox, and the timeline shows every invocation. One curl line per job, no agent to install, no port to open.

Integrate in one line

Drop a curl call at the end of any cron entry. Success and failure both ping Alarum so you have one timeline per job. Replace <YOUR_TOKEN> with an ingestion token from your project, then send.

# crontab -e
*/5 * * * * /usr/local/bin/backup.sh \
  && curl -s -X POST https://alarum.me/h \
       -H "Authorization: Bearer <YOUR_TOKEN>" \
       -d '{"level":"success","title":"Backup ok","source":"cron"}' \
  || curl -s -X POST https://alarum.me/h \
       -H "Authorization: Bearer <YOUR_TOKEN>" \
       -d '{"level":"error","title":"Backup FAILED","source":"cron","tags":["backup"]}'

Why teams pick Alarum for this

notifications_active

Instant failure alerts

When a cron POSTs an error, push lands on your phone immediately. No more "I saw the email three days later".

history

Run history per job

One token per cron, one timeline per token. See exactly when each invocation succeeded or failed.

Search past runs

Find every run that touched a tag, a source or a level. Full-text search across messages too.

nights_stay

Quiet hours

Crons that succeed at 3 AM stay silent. Errors flagged critical still cut through.

shield

No inbound port

Your server pushes out. Nothing to expose, works behind any NAT or firewall.

forum

Forward to Discord/Slack

Mirror failures to your team channel while keeping the success noise in Alarum.

Why not just use X?

Healthchecks.io and similar tools focus on deadman checks (alert when a ping is missed). Alarum is the inverse: your cron tells Alarum what happened, and Alarum routes failures to push, Discord or Slack. Best fit when your crons reliably get to run but you want to know fast when they fail.

Related use cases

rocket_launch

CI/CD pipeline notifications

Push notifications for GitHub Actions, GitLab CI, Jenkins, CircleCI and any pipeline. Route build failures, deploy alerts and release events to a single inbox.

Server & service alert inbox

Pipe alerts from Nagios, Monit, custom shell checks or your own services to a single mobile-friendly inbox. Push notifications when something breaks, forwarders to Discord and Slack.

Try it free, no card

Get started