n8n Error Handling Default n8n node behavior: error → workflow halts → caller gets nothing useful. For unattended workflows (webhook APIs, scheduled jobs, queue workers), that default is wrong. The symptom is "the integration just stopped working" with no log, no message, no clue. This skill is about handling errors so failures are loud, structured, and recoverable. Or best case scenario, handled in a way where it self heals. Non-negotiables For any API-shaped workflow (webhook trigger paired with ): 1. Every fallible node's error output is wired, and both paths end at a . No hanging error br…