# What is an error workflow in n8n? > An n8n error workflow starts with the Error Trigger and alerts you when another workflow fails. What it means, how to set it, and why tests don't fire it. Source: https://learn.ynteractive.com/content/glossary/error-workflow · Updated 2026-10-17 · Free from Stepthrough (https://learn.ynteractive.com) [n8n and automation](https://learn.ynteractive.com/content/glossary#topic-n8n-and-automation) · [AI glossary](https://learn.ynteractive.com/content/glossary) Quick answer An error workflow in n8n is a separate workflow that starts with the **Error Trigger** node and runs whenever another workflow fails. You pick it in that workflow's settings, and it usually sends you an email or message with the failed workflow's name, the error and a link to the run. Last updated October 17, 2026 [Take the free module →](https://learn.ynteractive.com/courses/n8n-jump-start/7)Module 7 of the free [n8n Jump Start](https://learn.ynteractive.com/courses/n8n-jump-start) course, about 10 minutes. No account needed. Updated October 17, 2026 · By [Robert Breen](https://learn.ynteractive.com/content/about) ## Why it matters for a small business n8n does not tell you when a published workflow fails. It adds a red line to the Executions list and waits for someone to look. For a small business that can mean a week of missed price updates or unsent reminders before anyone notices. One error workflow can watch every workflow you own. A few minutes of setup turns silent failures into an email you read the same morning. It is the alert half of [error handling](https://learn.ynteractive.com/content/glossary/error-handling); retries are the other half. ## In a real lesson: Get Alerted When an n8n Automation Fails, and Let It Retry by Itself In the [n8n error handling lesson](https://learn.ynteractive.com/content/n8n-error-handling-retry-on-fail-error-workflow), Maple Lane Florist, a made-up shop, has a Supplier price check workflow that failed one morning without anyone knowing. You create a workflow called Error alerts, choose **Error Trigger** ("Triggers the workflow when another workflow has an error"), and add Gmail **Send a message** using **{{ $json.workflow.name }}**, **{{ $json.execution.error.message }}** and **{{ $json.execution.url }}**. In the closing checklist you publish Error alerts, open Supplier price check's **Settings**, pick it under **Error Workflow (to notify when this one errors)**, save, and publish again so the live version uses the setting. [Try this lesson free](https://learn.ynteractive.com/modules/n8n-error-handling) or [read the step-by-step guide](https://learn.ynteractive.com/content/n8n-error-handling-retry-on-fail-error-workflow). ## How AI helps I add one AI step to my error alerts: a model reads the error message and writes one plain sentence on the likely cause, like "the supplier's server was busy" or "the Google login expired." The raw error and the run link stay in the email, so the guess never replaces the facts. Build the alert first in the [error handling lesson](https://learn.ynteractive.com/content/n8n-error-handling-retry-on-fail-error-workflow). ## Common confusions ### Error workflow vs Retry On Fail [Retry On Fail](https://learn.ynteractive.com/content/glossary/retry-on-fail) tries one step again before the run fails. The error workflow runs after the run has failed, to tell you. ### Why a test didn't fire it Error workflows only run for automatic, production runs. A manual test with [Execute workflow](https://learn.ynteractive.com/content/glossary/execute-workflow) never triggers one. ## Tips - [Publish](https://learn.ynteractive.com/content/glossary/publish-workflow) the error workflow first; the Error Workflow list only offers published ones. - A step set to Continue (using error output) no longer fails the run, so give that output its own alert. ## Related terms [Error handling](https://learn.ynteractive.com/content/glossary/error-handling) · [Retry On Fail](https://learn.ynteractive.com/content/glossary/retry-on-fail) · [Execution](https://learn.ynteractive.com/content/glossary/execution) · [Publishing a workflow](https://learn.ynteractive.com/content/glossary/publish-workflow) · [Execute workflow](https://learn.ynteractive.com/content/glossary/execute-workflow) · [Trigger](https://learn.ynteractive.com/content/glossary/trigger) ## More n8n and automation terms [Execute step](https://learn.ynteractive.com/content/glossary/execute-step) · [Execution (n8n)](https://learn.ynteractive.com/content/glossary/n8n-execution) · [Expression](https://learn.ynteractive.com/content/glossary/expression) · [Fallback output](https://learn.ynteractive.com/content/glossary/fallback-output) ## Where you use it: free lessons - [Get Alerted When an n8n Automation Fails, and Let It Retry by Itself](https://learn.ynteractive.com/content/n8n-error-handling-retry-on-fail-error-workflow) (n8n, 10 min) ## Frequently asked questions **What does Error Trigger mean in n8n?** It is the start node of an error workflow. It fires when a workflow that points to it fails, and passes along the workflow name, the error and the run link. **Why didn't my n8n error workflow run?** Usually the run was a manual test, the failed workflow does not have it picked in Settings, or the failed step used Continue or an error output, so the run did not fail. **Can one error workflow cover all my workflows?** Yes. Pick the same error workflow in each workflow's Settings. [All AI glossary terms, A to Z](https://learn.ynteractive.com/content/glossary) · [Free prompt templates](https://learn.ynteractive.com/content/prompts)