How to Set Up n8n Error Notifications in 10 Minutes (Error Trigger Guide)

Here’s the scenario: it’s 3 AM, your n8n workflow that syncs orders to your accounting system fails on a malformed payload, and nobody notices until a customer emails you a week later. This is the most common — and most expensive — failure mode in n8n.

The fix is one workflow, built once, that catches failures from every workflow on your instance. Here’s how to set it up in about ten minutes.

What you need

• An n8n instance (Cloud or self-hosted)
• A place to send alerts: Slack webhook, email (SMTP), or Telegram bot

Step 1: Create the Error Trigger workflow

Create a new workflow and add an Error Trigger node. That’s it — no configuration needed. The Error Trigger fires automatically whenever any other workflow on your instance fails. One trigger, all workflows.

Name the workflow something obvious like “Failure Notifier” so it’s easy to find.

Step 2: Format the error message

Add a Code node after the trigger and build a readable message. The Error Trigger provides the failing workflow’s name, the node that failed, the error message, and the execution ID. A good format:

⚠️ n8n workflow failed
Workflow: {{ $json.workflow.name }}
Node: {{ $json.node.name }}
Error: {{ $json.error.message }}
Execution: {{ $json.execution.id }}
Time: {{ $json.time }}

Include the execution ID — it’s the link to the full execution log, which is where you’ll actually debug.

Step 3: Send the alert

Add the notification node for your channel:

• Slack: Slack node → Post message to a channel, using an incoming webhook or the Slack app credential.
• Email: Email/SMTP node → send to your inbox. Keep the subject line short: “n8n FAILED: [workflow name]”.
• Telegram: Telegram node → send to your chat.

Test it by deliberately failing a workflow — add a node that throws an error, run it, and confirm the alert arrives. Then remove the test node.

Step 4: Make sure your workflows are set to notify

By default, n8n workflows notify the Error Trigger on failure. If you’ve disabled that per-workflow, re-enable it: Workflow settings → “Notify on error” (or the equivalent in your version).

What this gets you

From now on, every failure on your instance — in every workflow, including sub-workflows — lands in your inbox with the workflow name, the failing node, and the execution ID. Silent failures become impossible. You’ll know about problems at 3 AM instead of a week later.

This is the single highest-ROI pattern in n8n. If you only do one thing from this guide, do this.

Go deeper

I wrote a full $1 guide on n8n error handling — including retry strategies with exponential backoff, honest webhook status codes, and the exact Error Trigger setup for self-hosted instances. Plus 91 more guides on the nodes I use in production.

Browse all 92 n8n guides for $1 each

Frequently asked questions

Does the Error Trigger catch failures in sub-workflows?

Yes — when configured correctly, it fires on failures from sub-workflows too.

Will I get spammed with alerts?

Only when something fails. If you’re getting too many alerts, that’s a signal your workflows are fragile — fix the root cause, don’t mute the alarm.

Does this work on n8n Cloud?

Yes — Error Trigger works identically on Cloud and self-hosted.