n8n Alerting Guide: Get Notified When Workflows Break

Monitoring without alerting is just logging. You need notifications that reach you where you work — not inside a dashboard you check once a week. Here's a practical guide to setting up alerts for your n8n workflows.

Native options inside n8n

n8n has an Error Trigger node you can add to individual workflows. It fires when an execution fails, and you can route it to email, Slack, or any webhook endpoint. The setup is straightforward: create a new workflow with the Error Trigger, connect it to a Slack node, and assign it as the error handler for each production workflow.

The limitation is coverage. You have to assign this error workflow to every single production workflow manually. If you add a new workflow next month and forget to wire up the error handler, it runs unmonitored. And if n8n itself goes down or a cron trigger misses its schedule, the Error Trigger has nothing to fire on.

External alerting with RootBrief

RootBrief works from outside your n8n instance, polling the API at regular intervals. This means it catches things the Error Trigger can't: workflows that stopped running entirely, schedules that silently missed, and process-level failures where n8n itself wasn't available to fire a trigger.

Alerts go to email on the Free plan, and to Slack on the Pro plan ($19/mo). The Pro plan also generates weekly summary reports — useful for teams that need a regular status check without logging into a separate dashboard.

What I'd recommend

Use both. Keep the Error Trigger for instant feedback inside specific high-priority workflows, and use RootBrief as a safety net that covers everything — including the failures you can't predict. That combination gives you fast feedback on known risks and broad coverage for the unknown ones.