n8n Slack Alert for Silent Workflow Failures (Hourly)

Detect silent workflow failures every hour—and alert Slack when data comes back empty

This n8n workflow runs hourly to catch “silent failures” where a data-fetch step returns zero or incomplete items. When suspicious results are detected, it posts an alert to Slack and then intentionally fails the execution so the run is marked red and can trigger an Error Workflow.

What this workflow does

• Runs on a schedule: executes every hour automatically.
• Forces safe downstream output: your data retrieval step is configured to still output data so guard checks run even when no records are returned.
• Validates the result: the workflow strips placeholder output, counts items, and checks for required fields such as id and email.
• Continues when healthy: if thresholds and required fields are satisfied, the workflow completes normally.
• Alerts on silent failure: if the result looks suspicious (e.g., too few items or missing required fields), it sends a formatted “silent failure detected” message to your configured Slack channel.
• Stops with an error after alerting: the workflow uses a stop-and-error pattern so you get a red run and can escalate via an n8n Error Workflow.

Use cases

• Hourly monitoring of APIs where failures might return empty arrays instead of hard errors.
• SaaS operations workflows that require id and email fields to proceed reliably.
• Automation engineers who want Slack notifications plus red-run visibility for data-fetch anomalies.

Technical details

• Workflow type: n8n automation workflow for silent failure detection (tested on n8n 2.34.4, self-hosted).
• Nodes used: if, code, no op, Slack, sticky note, stop and error.
• Setup: replace the sample “Your data step” with your real data-fetch nodes, keep “always output data,” update guard thresholds, and configure a Slack credential and target channel (e.g., #alerts).
• Optional escalation: configure an n8n Error Workflow to receive the forced failure.