The useful result
Receive a clear message with the workflow name, failed step and a link whenever an automation fails.
- Receive a clear message with the workflow name, failed step and a link whenever an automation fails.
A lead form stops reaching your spreadsheet on Tuesday and you notice on Friday. Silent failure is the most expensive kind. n8n has a built-in way to run a second workflow whenever the first one fails, and it needs only a trigger, a message node and one setting.
This lesson builds a reusable error workflow and attaches it to your automations. You will test the alert deliberately, because an alert you have never seen fire is only a hope.
The examples below are illustrative exercises, not recorded results from any tool. Sources were checked on 24 October 2026; menus, limits and prices change, so confirm details on the linked pages.
Before you start
- An n8n instance with at least one working workflow
- A place to receive alerts, such as email, Slack or Telegram, already connected in n8n
- A copy of a workflow you can break on purpose
Review evidence
Documentation-based review · 2026-10-24
Primary documentation and official guidance checked on 24 October 2026. Examples, checks and exercises are original illustrations, not recorded tool tests. Cover artwork is a conceptual illustration.
Create an error workflow that starts with the Error Trigger
Make a new workflow whose first node is the Error Trigger and save it with a name like “Error Handler”. Add your message node after it. The trigger supplies the failed workflow’s name, the error message, the last node that ran and the execution URL, so use those fields in your alert text.
Write a short alert message template for an automation failure. Include these fields: workflow name, last node executed, error message, execution URL, time. Plain text, under 60 words, no emoji. Put the most urgent fact first.Example / expected result
Illustrative example; not a recorded model result.
“Workflow ‘Lead intake’ failed at node ‘Google Sheets’: Invalid credentials. Open the run: [execution URL].”
Check your result
The new workflow starts with the Error Trigger and ends with a message node that includes the workflow name, error message and execution link.
Attach it to each workflow you care about
Open the workflow you want to monitor, go to Options, then Settings, and choose your error workflow in the Error workflow field. Save. One error workflow can serve many workflows, so connect every automation that touches customers, money or data.
Check your result
Every important workflow shows your error workflow in its settings.
Break a copy on purpose and watch the alert arrive
Duplicate a workflow, add a Stop And Error node with a clear message, attach the error workflow and run it. Confirm the alert arrives in your inbox or chat within a minute and that the link opens the failed run. Delete the test copy afterwards.
Check your result
You received the test alert and the link opened the failed execution.
When it goes wrong
If the failure happens in a workflow’s trigger node, the alert carries less detail because the workflow never ran. An alert channel that is muted or full defeats the purpose, so test it again after you change accounts. Do not paste secrets or customer data into the alert message.
Make it your own
Attach the error workflow to two real automations, trigger a deliberate failure in a copy of each, and write down how long each alert took to reach you.
Useful next resources
Sources and review
Last checked Oct 24, 2026. Features and account limits can change. Verify important results against your original material.
Did this help you complete your task?
Tell us what needs improving. No account or private output required.
Report incorrect information or a broken linkGenius Forges Editorial
Practical AI lessons with checked sources, labelled examples and human verification.
