The Canary Workflow: A Fake n8n Job That Pages Me Before Clients Notice
Описание и применение
Проблема: клиентские рабочие процессы в n8n могут падать без видимых сигналов. Решение: ежечасный «канарейка»‑workflow, проверяющий LLM‑API, Gmail, webhook и сам API n8n, с оповещением в Telegram. За шесть месяцев он обнаружил четыре инцидента раньше клиентов, предотвращая жалобы.
Задача
Client workflows can fail silently on the platform layer, causing clients to notice outages before the owner does.
Результат
In six months the canary detected four incidents—revoked OAuth token, model deprecation, queue backup, TLS cert expiry—before any client noticed, preventing any client complaints.
Рабочий процесс
- Schedule canary to run hourly
- Probe LLM API with 10‑token prompt and 30s timeout
- Probe Gmail by sending and searching for a unique email
- Probe webhook by POSTing signed payload and checking 200 within 10s
- Probe n8n API for own execution history
- Log results and page via Telegram on failure
- If two probes fail, start 15‑minute re‑check loop
Доказательства
The canary tells me first, every time.
The canary runs every hour and produces nothing of value. Its only job is to touch the four things every real workflow in my fleet depends on: LLM API, Gmail round‑trip, Webhook echo, n8n API self‑query.
In six months, four real incidents — and in all four, the canary paged me before any client noticed.
Rule 1: the canary must be cheaper than what it protects.
- Дата записи: 2026-10-18T02:56:01.215Z