How do I get a Slack alert when an n8n workflow fails?

Add an Error Trigger node to a workflow, connect a Slack node after it, and activate it — n8n runs it whenever another workflow errors. Or connect the instance to Snuffler and select Slack as an alert channel for automatic coverage of every workflow.

How do I know if a scheduled n8n workflow stopped running?

The Error Trigger only fires on errors, not on runs that never happened. To catch a stopped schedule you need a monitor that compares expected schedules against actual executions and alerts on the gap — Snuffler does this as a missed-schedule alert.

How do I avoid being spammed by repeated alerts?

Use a tool that de-duplicates with a cooldown per workflow per alert type, so a flapping workflow produces one notification per incident rather than one per retry.

How to Get Notified When an n8n Workflow Fails

By Liran Udi·June 9, 2026·5 min read

To get notified when an n8n workflow fails, either add an Error Trigger node connected to a Slack/email node inside n8n, or connect your instance to a monitor that watches the executions API and alerts you on any failure. A dedicated monitor also catches schedules that never ran — something the Error Trigger can't — and explains why the run failed.

Option 1: n8n's Error Trigger node

The fastest built-in option. Create a new workflow, add an Error Trigger node as the start, then add a Slack, email, or HTTP Request node after it. n8n automatically runs this workflow whenever another workflow throws an error.

New workflow → add Error Trigger.
Add a Slack/Email/HTTP node and map in the error fields (workflow name, error message, node).
Activate it. For per-workflow control, set each workflow's "Error Workflow" in its settings.

Limits: it only fires on hard execution errors. It won't tell you a scheduled workflow simply never ran (a stopped trigger, a paused workflow, an unreachable instance), and it gives you no history or success-rate trend.

Option 2: catch the failures the Error Trigger misses

The most damaging incidents are often the silent ones — a workflow that should run every hour and just stops. Detecting that requires comparing expected schedules against actual executions, which a monitor does by polling the executions API. It can alert on:

Failed executions — like the Error Trigger, but across every workflow automatically.
Missed schedules — expected-but-absent runs.
Failure spikes — a workflow whose error rate suddenly climbs.
Instance down — the whole n8n instance became unreachable.

Where alerts should go

Send alerts to the place your team already watches, and avoid alert fatigue:

Slack for the team channel you live in.
Email for a paper trail or for clients who want it.
Webhook to route into PagerDuty/Opsgenie or your own tooling.

Good alerting also de-duplicates: one notification per incident, not one per retry. Snuffler applies a cooldown per workflow per alert type so a flapping workflow doesn't bury you.

Make alerts actionable, not just loud

A raw stack trace at 2 a.m. isn't much help. Snuffler attaches an AI-written, plain-English explanation of what went wrong and a suggested fix to each alert, so even a junior team member can triage quickly.

Set it up in minutes

Connect each n8n instance to Snuffler with a read-only API key, pick your alert channels, and you'll be notified — with context — the moment a workflow fails or misses its schedule. No workflow changes required.

Get failure alerts with Snuffler

Frequently asked questions

How do I get a Slack alert when an n8n workflow fails?: Add an Error Trigger node to a workflow, connect a Slack node after it, and activate it — n8n runs it whenever another workflow errors. Or connect the instance to Snuffler and select Slack as an alert channel for automatic coverage of every workflow.
How do I know if a scheduled n8n workflow stopped running?: The Error Trigger only fires on errors, not on runs that never happened. To catch a stopped schedule you need a monitor that compares expected schedules against actual executions and alerts on the gap — Snuffler does this as a missed-schedule alert.
How do I avoid being spammed by repeated alerts?: Use a tool that de-duplicates with a cooldown per workflow per alert type, so a flapping workflow produces one notification per incident rather than one per retry.