Know when your workflow fails before your client does

Here’s a scenario. You build a workflow, it works in testing, you hand it over, and a week later an API changes or a login expires. The workflow quietly stops, and nobody notices until a client asks why no leads came through.

n8n has a built-in fix that takes about five minutes.

Create a new, separate workflow and start it with an Error Trigger node. This node fires whenever another workflow fails.
Connect it to something that tells you, like an email, Telegram or Slack message. Include the workflow name, the error message, and the link to the failed execution. The Error Trigger gives you all of those.
Open your main workflow, go to its settings, and choose that workflow as the Error Workflow.

Now any time your main workflow breaks, you get a message with exactly what failed and where, and you can fix it before anyone else notices.

One thing that trips people up: this only fires on live, automatic runs, not when you click “Test workflow”. So don’t panic if your test failures don’t trigger an alert.

You can use a single error workflow for all your automations, so you only build it once. If you ever do client work, this is one of the easiest ways to look reliable.

My personal experience : At the start, I intended to implement all workflows of a project in a single canvas but faced difficulty in finding where it went wrong and later I created different workflows. When something failed, I knew which stage it was in straight away, instead of searching through one huge canvas for the broken node and created a small error workflow to log/monitor and alert when something failed. Smaller workflows are also easier to test, update and hand over.

Do you currently have any way of knowing when your workflows fail? Tell me in the comments, and if you don’t, set this up today.

16 comments

Know when your workflow fails before your client does