Workflow Error Notifier → Slack
Attach this to every workflow you run. Any failed execution posts to Slack with the failing node, the error and a direct link to the execution.
The problem
An unmonitored automation does not announce its own failure. It stops working silently, and you find out when a client asks why nobody followed up with the leads from last Tuesday. Third-party APIs change, plan limits get hit, and a renamed field breaks a mapping, and none of it raises a flag on its own.
What this workflow does
This is the workflow we attach to every build. Set it as the Error Workflow in each of your other workflows and n8n routes failures to it automatically. It flattens the deeply nested error payload defensively, truncates the message to something Slack will actually render, and links straight to the failed execution.
How it works
- Import it once and set it as the Error Workflow on your other workflows.
- n8n routes any failed execution to it automatically. No webhook to configure.
- A Code node flattens the nested error payload and handles missing fields.
- A Slack message posts with the workflow name, failing node, timestamp and error.
- The message links directly to the execution so you can debug from the alert.
What it connects
- n8n
- Slack