n8n Workflow Never Started: Build a Dead-Man's Switch
Solve silent failures in n8n where workflows never trigger by building a custom watchdog workflow with Gmail alert integration.

Stock photo for illustration only, not from the actual event
- n8n Error Trigger only fires on actual failures, leaving silent non-starts completely unnoticed.
- A Dead-Man's Switch watchdog checks execution logs on a schedule to alert you of prolonged inactivity.
- The setup consists of five working nodes requiring standard CONFIG and Gmail credentials.
- The author is a verified creator on the official n8n template library with seven live templates.
A common blind spot in n8n automation is that the Error Trigger node only activates when a workflow run explicitly fails. If a workflow never starts at all—due to a dead cron schedule, a changed webhook URL, or a deactivated workflow following an edit—it produces zero runs, zero errors, and zero alerts, leaving you completely in the dark.
The effective workaround is a dead-man's switch: a secondary watchdog workflow that periodically queries the executions list and alerts you when the monitored workflow goes quiet for too long, transforming "no run at all" into a valid alerting condition.
This watchdog setup requires five working nodes plus configuration. For delivery, the Gmail node must be wired properly, and you should run a manual test alert to confirm receipt before deployment. Note that this watchdog is independent and is not included in the free starter pack or paid workflow packs.

Stock photo for illustration only, not from the actual event
To implement it, paste the code into n8n via Import from file, then populate the CONFIG section and provide your Gmail credentials. All placeholder secrets in the file ensure no sensitive data is exposed during the setup process.
Implementing a Dead-Man's Switch is an essential architecture pattern in workflow automation. While standard error handling catches explicit exceptions, watchdog patterns safeguard against silent infrastructure failures where scheduled tasks simply vanish without triggering any log entries.
The author is recognized as a verified creator on the official n8n template library, maintaining seven active workflows including workflow-02, workflow-03, workflow-04, workflow-07, OB-01, workflow-01, and workflow-11, alongside providing additional starter resources.
Source: Dev.to
Found something wrong in this article? Report an issue with this article
Comments
Leave a Comment