n8n Silent Workflow Failure Monitor + Slack Alerts via API

Catch Silent n8n Failures Early — with Slack Alerts

This n8n workflow runs hourly to monitor your active workflows via the n8n API, detects silent failure patterns (missed schedules, empty runs, and repeated errors), and posts only new issues and recoveries to your Slack channel.

What this workflow does

• Checks on a schedule: Uses a Schedule Trigger to run every hour.
• Loads configuration + thresholds: Reads alert settings such as your Slack channel, a skip tag (default: no-monitor), and optional quiet-hour overrides for specific workflows.
• Pulls runtime data from n8n: Uses the n8n API to list all active workflows and fetches the 10 most recent executions (with data) for each workflow.
• Detects silent failure patterns: Analyzes executions to identify:
  • Missed schedule windows
  • Consecutive successful runs that produce zero items
  • Repeated execution failures
• Alerts only what’s new: Compares findings against stored alert state so it posts only new/changed issues and sends a recovery message when the workflow returns to normal.
• Posts a single summary: Sends one consolidated message to Slack whenever there’s anything new to report.

Use cases

• SaaS operators monitoring critical automations that must run on time.
• Automation engineers spotting workflows that “look green” but stop producing results (empty successful runs).
• Teams preventing alert fatigue by excluding workflows with the no-monitor tag and using quiet-hour overrides.

Technical details

• Integrations/Credentials: n8n API key (added as an n8n API credential for the workflow/execution reader nodes) + Slack credential.
• Nodes/tech stack: Schedule Trigger, Set, Code, Slack, plus a Sticky Note for inline guidance.
• Execution logic: n8n API workflow listing + latest execution fetch, analysis, state comparison, and Slack alert posting.