Documentation

Get started

Gonewatch watches expected events — cron jobs, backups, pipelines, scheduled workflows. You POST when the job succeeds. Silence is the Down alert.

Step 1
Create a monitor
Fixed time of day or a rolling interval, plus a grace window.
Step 2
Copy the URL
Each monitor has a secret heartbeat URL. Treat it like an API key.
Step 3
POST on success
Empty body is enough. Optional JSON is stored for charts.

Your first ping

After the job exits successfully, POST to the URL from the monitor page. Replace the token. Do not commit it.

nightly-backup.sh

curl -fsS -X POST https://gonewatch.com/api/heartbeat/YOUR_TOKEN \
  -H "Content-Type: application/json" \
  -d '{"duration_ms":184320,"bytes":2147483648,"tables":42}'

Ping only on success

Chain the request after the job, or use if: success() in GitHub Actions. A failed dump that still pings looks healthy.

What you get

Email on Down and recovery. Slack, Discord, Telegram, GitHub Issues, Linear tickets, and reminders on Basic and Pro.
Last payload, sparklines, and expandable ping history on the monitor — clipped to your plan window (7 / 90 / 365 days).
Copy-paste snippets for cURL, Node, Python, and the GitHub Action.

Create a monitor Heartbeat API

Job-specific walkthroughs: cron, backups, GitHub Actions.

Alerts