Monitor stale workflows via the n8n API and send alerts to Slack or Telegram
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
Nodes used (6)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Code
n8n-nodes-base.code - HTTP Request
n8n-nodes-base.httpRequest - Slack
n8n-nodes-base.slack - Telegram
n8n-nodes-base.telegram - Send Email
n8n-nodes-base.emailSend
What it does
Quick Overview This workflow runs hourly to check the last successful execution time of selected n8n workflows via the n8n REST API, and sends an alert (Slack by default, or Telegram, email, or WorkflowBuddy push) when any workflow has gone stale past its allowed threshold. How it works 1. Runs every hour on a schedule. 2. Builds a list of workflow IDs and per-workflow maximum age thresholds, along with your n8n base URL. 3. Queries the n8n REST API for the most recent successful execution of each monitored workflow. 4. Calculates how long it has been since the last success (or treats it as stale if there is no successful execution on record). 5. Sends one alert per stale workflow to Slack (and optionally Telegram, email, and/or WorkflowBuddy iOS push). Setup 1. Update the n8n base URL and the monitored workflow list (workflowId, workflowName, and maxAgeHours) in the configuration code. 2. Create an n8n API key and add it to an HTTP Header Auth credential named X-N8N-API-KEY, then select it for the n8n API request. 3. Configure at least one alert channel: connect Slack and set the target channel, or enable Telegram/email/WorkflowBuddy and fill in the required chat IDs, addresses, and header auth token.