n8n: Get Alerted When an Automation Fails, Before a Client Notices

Description and use

In n8n, configuring automated alerts for workflow failures and retry logic ensures quick response to errors, preventing incorrect data from reaching clients.

Problem

A silent failure in an n8n workflow can cause incorrect data to be used and clients to receive wrong information, leading to costly errors.

Outcome

The setup ensures that any workflow failure triggers an immediate notification and that transient errors are retried automatically.

Workflow

• Create an error workflow with an Error Trigger node.
• Add a Gmail or Slack node that sends the workflow name, time, and error text to an operator.
• Open each important workflow’s settings and select the error workflow as the error handler.
• Run a test failure on purpose, verify the alert arrives, then delete the test.

Evidence

A silent failure costs more than an error. Say your n8n workflow pulls prices from a sheet every morning, and one run fails on a Monday.

Source

The business case is simple: a failed run should tell a person within minutes, and a step that fails for a passing reason should retry on its own.

Source

Build a second workflow that starts with the Error Trigger node. When any workflow fails, it runs, reads the failed workflow's name and the error message, and sends one email or chat message.

Source

If the same step fails three times in a row, that is an alert, not a success. Keep the alert, and fix the cause.

Source