n8n Monitoring7 min read

How to Get n8n Alerts in Slack: A Practical Setup Guide

Email alerts are fine until your inbox has 200 unread messages and a failed workflow notification is buried somewhere on page three. If your team lives in Slack, your alerts should live there too. Here's how to get n8n failure notifications into Slack — two ways, with different trade-offs.

Method 1: DIY with n8n's Error Trigger

Create a dedicated "Alert Router" workflow in n8n. Add an Error Trigger node as the start, connect it to a Slack node that posts to your #alerts channel, and configure the message to include the failed workflow name, error message, and timestamp. Then go to every production workflow, open Settings, and assign this alert workflow as the error handler.

It works. The downsides: you have to touch every workflow individually, new workflows don't inherit the error handler automatically, and if n8n itself goes down, the Slack node can't fire because it's inside the same n8n instance that's broken.

DIY n8n Slack alert flow using Error TriggerError Triggern8n built-inFormat Messageworkflow + error + timeSlack Node#alerts channel⚠ Only works if n8n is running and error handler is assigned to each workflow
The DIY approach works but has gaps in coverage

Method 2: External monitoring with Slack integration

RootBrief's Pro plan ($19/mo) includes native Slack integration. You connect your Slack workspace once, pick a channel, and every failure alert goes there automatically — for all workflows, including ones you add later. No per-workflow configuration needed.

The key difference: RootBrief runs outside your n8n instance. So even if n8n crashes or a workflow silently stops running, the alert still reaches Slack. It also sends weekly summary reports to Slack, which gives the team a quick "everything is fine" or "here's what broke this week" without anyone needing to check a dashboard.

DIY vs RootBrief Pro Slack alerting comparisonDIY (Error Trigger + Slack)✓ Free✗ Per-workflow setup required✗ Misses silent stops & crashes✗ Fails if n8n is downRootBrief Pro ($19/mo)✓ One-time Slack setup✓ Auto-covers all workflows✓ Works when n8n is down✓ Weekly summary reports
External Slack alerting eliminates the single point of failure

Which should you use?

If you have fewer than five workflows and a tight budget, the DIY approach is a reasonable start. Once you're past ten workflows or managing automations for clients, the external approach saves you from the maintenance overhead — and from the blind spots that the Error Trigger can't cover. Most teams find the $19/month worth it just for the "n8n is down and I still got a Slack alert" peace of mind.

Get n8n alerts in Slack without touching each workflow. RootBrief Pro plan includes native Slack integration — start free.

Monitor your n8n workflows in 2 minutes

RootBrief detects failures, explains root causes in plain English, and alerts your team via email or Slack.

Start free