Templates / Report daily workflow SLA metrics with the n8n API, data tables and Telegram

Report daily workflow SLA metrics with the n8n API, data tables and Telegram

Ready for 3.0

by Serhii Bondarenko ✓ · 38 views · created 2026-06-18 · DevOps

Ready 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.

What 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).

  1. Config (Edit Fields (Set)): sets 7 fields: windowHours, targetSuccessRate, targetP95Seconds…
  2. Get all workflows (n8n): uses n8n
  3. Get recent executions (n8n): work with execution
  4. Combine workflows and executions (Merge): merges the data from its input branches
  5. Aggregate metrics (Code): runs custom JavaScript code
  6. Detect stalled schedules (Code): runs custom JavaScript code
  7. Evaluate SLA (Code): runs custom JavaScript code
  8. Get previous snapshot (Data table): get
  9. Compare to previous run (Code): runs custom JavaScript code
  10. Save snapshot (Data table): uses Data table

…plus 3 more steps. See the full node list below.

Services it uses

Telegram

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)

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…

Excerpt from Serhii Bondarenko's description on n8n.io.

View the original on n8n.io → Check your own copy

Get the weekly “what broke” email

New templates, newly broken ones, and n8n release changes. One short email a week.

Form not loading? Subscribe here.