How to Handle Errors in n8n with an Error Workflow

A workflow that fails silently is dangerous. Plan for failure.

Error workflow

Create a separate workflow that starts with the Error Trigger node. In the settings of your other workflows, choose it as the error workflow. When any of them fails, it runs and receives details of what went wrong.

What to do in it

Send an alert by email or Telegram with the workflow name, the failing node and a link to the execution (Telegram bot).

Retries

Many nodes allow retry on failure with a wait. Use it for temporary problems like timeouts, not for wrong data.

Handle expected problems

Use IF checks before risky steps, such as a missing email, and the Stop and Error node when data is unacceptable.

Continue on fail

Some nodes can continue when an item fails. Use it deliberately and log the failures.

Test failure

Break something on purpose and confirm the alert arrives.

Related

Debugging executions.

Quick answers

What is an error workflow?

A workflow with an Error Trigger that runs when another workflow fails.

Should I retry failed nodes?

For temporary problems, yes; not for wrong data.

How do I test it?

Break something deliberately and confirm the alert.


Related reading

Prefer feedback on your own workflows?

In our live n8n classes you build workflows alongside a trainer who reviews your work. It is a practical 15-day program for beginners to advanced learners.

See the 15-day n8n training  |  Find your city  |  Book free counselling

Want to learn n8n hands-on?

Join our 15-day live, trainer-led n8n training.

Book Free Counselling
WhatsApp Call Enquiry

Request A Callback

Talk To Our Expert

We use your details only to contact you about this training.