Report daily workflow SLA metrics with the n8n API, data tables and Telegram
Ready for 3.0What this workflow does
This workflow has 14 nodes and runs on a schedule (every day at 08:00). Along the way it connects Telegram.
How it runs
Trigger: On a schedule (every day at 08:00).
- Config (Edit Fields (Set)): sets 7 fields: windowHours, targetSuccessRate, targetP95Seconds…
- Get all workflows (n8n): uses n8n
- Get recent executions (n8n): work with execution
- Combine workflows and executions (Merge): merges the data from its input branches
- Aggregate metrics (Code): runs custom JavaScript code
- Detect stalled schedules (Code): runs custom JavaScript code
- Evaluate SLA (Code): runs custom JavaScript code
- Get previous snapshot (Data table): get
- Compare to previous run (Code): runs custom JavaScript code
- Save snapshot (Data table): uses Data table
…plus 3 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (7)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Edit Fields (Set)
n8n-nodes-base.set - n8n
n8n-nodes-base.n8n - Merge
n8n-nodes-base.merge - Code
n8n-nodes-base.code - Data table
n8n-nodes-base.dataTable - Telegram
n8n-nodes-base.telegram
From the author
Quick overview This workflow runs daily, queries the n8n API for workflows and recent executions, calculates per-workflow success rate, error count and p95 runtime over a rolling window, detects stalled schedules, stores a snapshot in an n8n Data Table, and…