What it does
Monitors scheduled n8n workflows and pings ops if a run is missed or errors, providing logs and retry links.
Why I recommend it
Silent automation failures cause downstream data issues. Monitoring keeps trust high.
Expected benefits
- Faster recovery from workflow failures
- Reliable automation SLAs
- Less manual checking of execution logs
- Documentation of incidents
How it works
Heartbeat workflow logs successes to database -> watcher checks for expected run frequency -> if missing/error, send Slack/Email with workflow name, timestamp, error message, and retry instructions.
Quick start
Enable n8n’s built-in error email notifications, then upgrade to full heartbeat monitoring.
Level-up version
Auto-retry safe jobs, escalate persistent failures, and log uptime metrics for stakeholders.
Tools you can use
Automation: n8n, Zapier
Monitoring: Healthchecks.io, Uptime Kuma
Messaging: Slack, PagerDuty
Also works with
Make schedules, cron jobs, Airflow DAGs.
Technical implementation solution
- No-code: n8n workflow -> HTTP Request to Healthchecks -> Slack alert on failure.
- API-based: Cron job queries n8n API -> stores run metadata -> triggers PagerDuty if anomaly detected.
Where it gets tricky
Handling intentionally paused workflows, distinguishing partial failures, and securing access to n8n logs.
