Analysis updated 2026-05-18
Share a live status page with clients so they can check if their n8n automations are running without logging into n8n.
Catch all n8n workflow failures with a single shared error workflow that reports everything to FlowWatch.
Track 30-day uptime and run history across multiple client workflows from one admin dashboard.
Expose client status pages over the internet using a Cloudflare tunnel without opening a server port publicly.
| el-sheikhai/flowwatch | arashthr/hugo-flow | argeneau12e/kairos-tx | |
|---|---|---|---|
| Stars | 2 | 2 | 2 |
| Language | TypeScript | TypeScript | TypeScript |
| Setup difficulty | moderate | moderate | hard |
| Complexity | 3/5 | 3/5 | 4/5 |
| Audience | pm founder | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires an existing n8n instance, each workflow needs an HTTP Request node added manually to report run status to FlowWatch.
FlowWatch is a self-hosted status page tool for people who run n8n automation workflows for clients. Instead of logging into n8n and taking screenshots every time a client asks if their automations are working, you give each client a shareable URL where they can see the live status of their workflows on their own. The tool runs as a single Docker container alongside n8n. Integration works through HTTP requests: you add a small "success" node to the end of each n8n workflow that sends a ping to FlowWatch whenever the workflow runs successfully. A separate error workflow, imported once, catches failures from all other workflows and reports those too. FlowWatch registers each workflow automatically the first time it receives a ping, so there is no manual setup on the FlowWatch side beyond the initial installation. The admin dashboard lets you create client accounts, each with their own isolated status page. You generate two tokens per client: a write token that goes into n8n's HTTP request nodes, and a read token that goes into the URL you share with the client. The client page shows color-coded status dots for each workflow, a 30-day uptime bar chart, and a list of recent runs. It supports both light and dark mode. The tool runs a Hono.js backend with a React frontend and stores data in SQLite, all within one Docker container with no external database required. It can be made publicly accessible using a Cloudflare tunnel. Security features include rate limiting on all API endpoints, content security policy headers, parameterized database queries, and running Docker as a non-root user. The license is PolyForm Noncommercial, which means the software is free for personal and non-commercial use but requires explicit permission for commercial deployment or resale.
A self-hosted status page for n8n workflows: give clients a URL showing live workflow health, run history, and 30-day uptime without granting them access to n8n.
Mainly TypeScript. The stack also includes TypeScript, React, Hono.js.
Free for personal and non-commercial use only, commercial use including resale requires written permission from the author.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly pm founder.
This repo across BitVibe Labs
Verify against the repo before relying on details.