explaingit

el-sheikhai/flowwatch

Analysis updated 2026-05-18

2TypeScriptAudience · pm founderComplexity · 3/5LicenseSetup · moderate

TLDR

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.

Mindmap

mindmap
  root((FlowWatch))
    What it does
      n8n status page
      Client dashboards
      Uptime tracking
    How it works
      n8n pings on run
      Auto-registration
      Read vs write tokens
    Tech Stack
      Hono.js
      React
      SQLite
      Docker
    Features
      Per-client isolation
      30-day uptime bars
      Dark and light mode
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Share a live status page with clients so they can check if their n8n automations are running without logging into n8n.

USE CASE 2

Catch all n8n workflow failures with a single shared error workflow that reports everything to FlowWatch.

USE CASE 3

Track 30-day uptime and run history across multiple client workflows from one admin dashboard.

USE CASE 4

Expose client status pages over the internet using a Cloudflare tunnel without opening a server port publicly.

What is it built with?

TypeScriptReactHono.jsSQLiteDockerDrizzle ORM

How does it compare?

el-sheikhai/flowwatcharashthr/hugo-flowargeneau12e/kairos-tx
Stars222
LanguageTypeScriptTypeScriptTypeScript
Setup difficultymoderatemoderatehard
Complexity3/53/54/5
Audiencepm founderdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 30min

Requires an existing n8n instance, each workflow needs an HTTP Request node added manually to report run status to FlowWatch.

Free for personal and non-commercial use only, commercial use including resale requires written permission from the author.

In plain English

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.

Copy-paste prompts

Prompt 1
Walk me through setting up FlowWatch next to my n8n instance using Docker Compose and connecting the first workflow to send status pings.
Prompt 2
How do I add the FlowWatch success HTTP ping node to an existing n8n workflow? What does the request body look like and where does the write token go?
Prompt 3
Set up the FlowWatch global error workflow in n8n so every workflow in my instance reports failures to the same FlowWatch client.
Prompt 4
How do I expose FlowWatch to clients over the internet using a Cloudflare tunnel without opening a public port on my server?

Frequently asked questions

What is flowwatch?

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.

What language is flowwatch written in?

Mainly TypeScript. The stack also includes TypeScript, React, Hono.js.

What license does flowwatch use?

Free for personal and non-commercial use only, commercial use including resale requires written permission from the author.

How hard is flowwatch to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is flowwatch for?

Mainly pm founder.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Scan in gitsafehub Deploy in gitdeployhub el-sheikhai on gitmyhub

Verify against the repo before relying on details.