By Brooke Houck, PhD · Last updated: August 25, 2026
These solve different problems. n8n's official community template #2669, "Auto-generate documentation for n8n workflows with GPT and Docsify," builds a browsable internal wiki of every workflow on your n8n instance, for your own team. n8n Client Ready is meant to generate one branded document for one automation, to hand to a non-technical client. If what you need is the first thing, use the free template — it's free, it's official, and it does that job well. If what you need is the second thing, the free template wasn't built for it, and that's the gap n8n Client Ready is trying to fill.
Template #2669 is a real, official n8n workflow, not a third-party knockoff. Installed and run, it walks your n8n instance, uses GPT to write a plain-language description of each workflow, and uses Mermaid.js to draw a diagram of its nodes and connections. The output is published into Docsify, a JavaScript site generator that turns Markdown files into a browsable documentation portal. The result is an internal wiki: every workflow you have, documented and searchable in one place, for whoever on your team needs to understand what's running.
To run it, you need a few things most non-developers won't have sitting around: an OpenAI API key (you pay for those GPT calls directly), your n8n instance's URL configured into the workflow, and write access to a project directory on a server somewhere to host the generated Docsify site. It's a workflow you configure and run yourself, on your own infrastructure. It's genuinely free — no subscription, no per-document charge — but it assumes an audience comfortable setting that up.
One thing worth flagging plainly, because it's in the template's own documentation, not a criticism I'm inventing: the generated Docsify editor ships with no authentication. If you publish the output somewhere reachable on the open internet without adding your own access control in front of it, anyone with the link can read — and depending on how you deploy it, potentially edit — your workflow documentation. That's a fine tradeoff for an internal tool behind a VPN or on a private server. It's a real risk if you're thinking about handing that link to a client.
n8n Client Ready is aimed at a narrower, more specific moment: you just finished building an automation for a client, and you need to hand them something that explains what it does, in language they can actually read, without teaching them what a webhook node is. The target output is one document — Markdown and PDF — per automation, meant to leave your hands and land in a client's inbox.
Concretely, once it ships, the plan is: upload a blueprint export (JSON) from n8n or Make, get back a document with a visual diagram of the flow, plain-language explanations of each step, and a list of the variables the automation uses, in about 60 seconds. It supports Make as well as n8n, which the official template doesn't, since the official template is naturally scoped to n8n's own product. There's no API key to bring, no server to host anything on, and no separate documentation site to stand up and secure — the output is a document, not a portal.
| n8n's free template (#2669) | n8n Client Ready | |
|---|---|---|
| Output | Internal Docsify wiki, all workflows | One document per automation (Markdown + PDF) |
| Audience | Your own dev/ops team | Your non-technical client |
| Platforms | n8n only | n8n and Make |
| Setup required | OpenAI API key, instance URL config, a place to host the site | None — upload a blueprint export |
| Cost | Free (you pay your own OpenAI usage) | Paid subscription |
| Diagrams | Mermaid.js, in the wiki | Included in the document |
| Access control | None by default (per the template's own docs) — you add it | N/A — it's a document you send, not a hosted site |
| White-label / branding | Not applicable | Yes, on the Agency plan |
| Status | Live today | Pre-order, delivery within 30 days of full launch |
If you're documenting your own team's n8n workflows for internal reference, and someone on your team is comfortable dropping in an API key and hosting a small static site, the official template is the better choice — full stop. It's free, it's maintained by n8n, and an internal wiki of every workflow is exactly the shape of thing it's built to produce. There's no reason to pay for something else to do that job.
The gap shows up specifically at the client handoff: you don't want to give a client credentials to a Docsify site that shows every automation you've ever built for anyone, you don't want to explain what an OpenAI API key is, and you don't want to be the one securing a documentation portal you stood up for someone else's benefit. That's a one-document, one-client problem, and it's the specific thing n8n Client Ready is being built for.