Give every n8n workflow an error workflow

When an n8n production execution fails, nothing happens unless you've told n8n where to send the failure.

The fix takes five minutes: build one workflow that starts with the Error Trigger node and sends an alert to Slack, email, or wherever your team actually looks. Include the workflow name, the failing node, the error message, and the execution URL, all of which the Error Trigger provides.

Then open each client workflow's Settings and pick that workflow as its Error workflow. One alerting workflow can serve all of them.

Note that error workflows don't fire for manual test runs, so test with a real trigger.

What this won't catch: runs that "succeed" while doing nothing. More on that in the next post.

Run the free n8n Health Check (no account needed): https://leadpulseops.com/health-check