Discofork
Repository brief

Zie619/n8n-workflows

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T13:02:56.394Z
3mo ago

Zie619/n8n-workflows

Zie619/n8n-workflows is a large collection of n8n automation workflows, described as "all of the workflows of n8n i could find" and presented as an online-browsable repository. It is very active in visibility terms, with 53,374 stars, 6,937 forks, and recent updates through 2026-03-30. The repo also includes a Python-based API/server stack, container and deployment files, docs, and workflow-related content, so forks may be interesting if you want to build on a large workflow catalog plus a surrounding web/app delivery setup.

GitHub
Loading tags...
Stars53,374
Forks6,937
Default branchmain
Last pushed2026-02-11T15:41:17Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Choose this fork if you value local search, filtering, visualization, and easy JSON export more than staying current with the largest upstream workflow archive. Choose upstream if breadth and freshness matter most.

Prefer upstream unless you specifically need this older snapshot. This fork does not add capabilities; it mainly preserves an earlier state of the same workflow collection.

Choose upstream unless you specifically want a snapshot you can pin and modify locally. This fork shows no clear added capability, while it is materially behind recent upstream updates.

Choose the upstream repo unless you specifically need this fork as a personal mirror or starting point. It does not show meaningful divergence, and it lags upstream enough that the parent is the better default for adopters.

Adopt this fork only if you need a simple mirror and do not care about being current. For most users, upstream is the better choice because this fork adds no visible functionality and is materially behind.

Prefer this fork if you want a Chinese-localized workflow library and can tolerate being materially behind upstream. Prefer upstream if you want the newest and broadest catalog plus ongoing repo-side improvements.

Prefer upstream unless you need this exact fork as a starting point; it does not add capabilities and is noticeably behind.

Prefer upstream unless you specifically want a frozen copy. This fork shows no added functionality and is 21 commits behind, so it is more a passive mirror than an improved distribution.

Choose this fork only if you want an almost-vanilla baseline; for anyone wanting the newest workflows, docs, and fixes, upstream is the better choice.

Prefer upstream unless you specifically want a frozen 2025-11-15 snapshot. This fork has no added capabilities and is materially behind the parent in documentation and repo polish.