How it works
A routine sends us a signal. A site, we call.
Connect a routine
- Name the routine
- Choose how often
- Add its signal link to the task
- Late? You get an alert
nightly-backup Healthy
- Expected signal
- Every 24 h
- Last signal
- 5 September 2026, 03:20 UTC
- Times late
- None
Example from a real routine.
Inspect your crontab
Paste crontab lines to check monitor names, secret redaction and the next UTC run before importing.
2 monitor(s) ready2 ignored
pg_dump app --password [redacted] > backup.sqlNext UTC run: 2026-11-13 03:00 UTC0 3 * * *curl -fsS https://example.com/healthNext UTC run: 2026-11-13 00:05 UTC*/5 * * * *
2 ignored
- Line 1 · comment:
# Daily PostgreSQL dump - Line 4 · @reboot has no fixed schedule:
@reboot /usr/local/bin/boot-hook.sh
Check a site
- Paste the site address
- Choose how often: 1 min to 1 h
- Two failed checks in a row confirm the fall
- E-mail or webhook when it goes down and when it is back
Send the first signal
After you create the routine, copy its link or command.
Backup or script
Send the signal after a successful run.
n8n, Make or Zapier
Last step: call the signal link.
Server signal
A schedule on the server sends a signal every few minutes.