FlowDocs — Drop Your n8n Export Folder, Get a Full Migration Playbook in 60 Seconds
You have 50 undocumented n8n flows, one engineer who built them all just quit, and your migration deadline is next sprint. FlowDocs is a CLI tool that reads your n8n export folder and outputs human-readable documentation, dependency maps, and a step-by-step migration playbook automatically.
Difficulty
beginner
Category
Developer Tools
Market Demand
High
Revenue Score
6/10
Platform
CLI Tool
Vibe Code Friendly
No
Hackathon Score
5/10
Validated by Real Pain
— sourced from real community discussions
Teams managing large undocumented n8n workflow libraries face migration and onboarding crises with no automated documentation or dependency mapping tooling available.
What is it?
Teams stuck on undocumented n8n setups face a brutal choice: spend weeks reverse-engineering flows before migrating or risk breaking production automations mid-sprint. FlowDocs is an npm CLI that scans an n8n export directory, extracts node types, data flows, and trigger conditions, then calls Claude to generate per-flow documentation, a cross-flow dependency graph, and a prioritized migration checklist formatted for Notion or Markdown export. Three commands and your ops chaos becomes a readable handoff doc. Ships fast because n8n exports are well-structured JSON and the CLI pattern avoids all frontend complexity.
Why now?
The May 2026 migration wave from Zapier and Make to n8n is peaking, and teams inheriting undocumented n8n setups from departed engineers are flooding automation subreddits with exactly this problem right now.
- ▸CLI command that parses an entire n8n export folder and generates per-flow Markdown documentation.
- ▸Cross-flow dependency map showing which flows trigger or depend on others as a Mermaid diagram.
- ▸Claude-powered migration playbook ranking flows by complexity and suggesting migration order.
- ▸Notion and Markdown export modes with front-matter metadata for direct Notion import.
Target Audience
Ops engineers and developers managing 20+ n8n workflows considering migration or new-hire onboarding, estimated 15,000+ teams in this situation globally.
Example Use Case
An ops lead runs npx flowdocs ./exports --output notion and receives a full Notion-ready documentation pack for all 50 flows including a dependency graph and migration priority ranking within 2 minutes.
User Stories
- ▸As an ops engineer inheriting an undocumented n8n setup, I want auto-generated flow documentation, so that I can onboard without spending a week reverse-engineering JSON.
- ▸As a team lead planning an n8n migration, I want a dependency map of all our flows, so that I can sequence the migration without accidentally breaking upstream triggers.
- ▸As a freelance n8n developer handing off a project, I want a one-command documentation generator, so that I can deliver a professional handoff package without writing docs manually.
Done When
- ✓Parser: done when CLI reads a 10-flow export folder and outputs one Markdown file per flow with node count, trigger type, and data flow summary.
- ✓Dependency map: done when output directory contains a valid Mermaid diagram file showing all inter-flow trigger relationships.
- ✓Migration playbook: done when Claude output includes a numbered migration order ranked by complexity with a one-sentence rationale per flow.
- ✓Export modes: done when --format notion flag produces files with valid Notion-compatible front-matter that import without errors into a Notion database.
Is it worth building?
$49 one-time x 100 customers = $4,900 in month 1. $99/month SaaS tier for teams wanting continuous re-scanning x 40 teams = $3,960 MRR at month 4. Math assumes 2% conversion from n8n Discord and Reddit.
Unit Economics
CAC: $5 via community posts. LTV: $49 one-time or $1,188 (12 months at $99/month) for team tier. Payback: immediate on one-time sales. Gross margin: 90%.
Business Model
One-time purchase plus SaaS upgrade
Monetization Path
$49 one-time CLI license via Gumroad or LemonSqueezy for solo users, $99/month team SaaS tier for CI/CD integration and continuous re-scanning.
Revenue Timeline
First dollar: day 5 via Gumroad post in r/n8n. $1k revenue: week 3. $3k MRR: month 4 via team SaaS tier.
Estimated Monthly Cost
Claude API: $30 (per-user key model reduces cost), LemonSqueezy fees: $10, Vercel for landing page: $0 free tier. Total: ~$40/month at launch.
Profit Potential
$3k–$8k MRR achievable within 4 months targeting active n8n migration projects.
Scalability
Medium — CLI is a stepping stone to a paid web dashboard product for ongoing workflow governance.
Success Metrics
Week 1: 50 npm installs. Month 1: 30 paid licenses. Month 3: 15 team SaaS customers.
Launch & Validation Plan
Post in r/n8n offering free CLI run for anyone who shares their export folder count, collect 10 DMs, validate the doc quality before charging.
Customer Acquisition Strategy
First customer: post a before/after screenshot in r/n8n showing undocumented flow JSON versus clean FlowDocs output, link to Gumroad in comments, first 5 sales come from that thread. Ongoing: n8n Discord, r/automation, npm organic discovery, Twitter/X dev community.
What's the competition?
Competition Level
Low
Similar Products
FlowAudit is SaaS-based and runtime-focused, not documentation-focused. MigrateFlow covers Zapier-to-n8n migration but not documentation generation. No npm CLI exists for this specific use case.
Competitive Advantage
The only CLI tool purpose-built for n8n export documentation — no setup beyond an API key, runs in 60 seconds, outputs formats ops teams already use.
Regulatory Risks
Low regulatory risk. CLI runs locally and only sends flow metadata to Claude API — recommend users review their n8n exports for sensitive data before running.
What's the roadmap?
Feature Roadmap
V1 (launch): parse, document, dependency map, Markdown export. V2 (month 2-3): Notion export, license key server, --watch mode for CI. V3 (month 4+): web dashboard, GitHub Actions integration, team SaaS tier.
Milestone Plan
Phase 1 (Week 1): parser, Claude integration, Markdown exporter shipped. Phase 2 (Week 2): npm publish, Gumroad license, r/n8n post live. Phase 3 (Month 2): 30 paid licenses, SaaS tier spec validated.
How do you build it?
Tech Stack
Node.js CLI, Commander.js, Claude API, gray-matter for Markdown output — build entirely with Cursor
Suggested Frameworks
-
Time to Ship
1 week
Required Skills
Node.js CLI development, Claude API prompting, JSON parsing.
Resources
n8n workflow JSON schema docs, Commander.js docs, Claude API docs, LemonSqueezy integration guide.
MVP Scope
bin/flowdocs.ts (CLI entry point with Commander.js), lib/parser.ts (n8n JSON export scanner), lib/graph.ts (dependency map builder and Mermaid generator), lib/claude.ts (Claude API doc generation client), lib/exporter.ts (Markdown and Notion format output), templates/flow-doc.md (Markdown template), package.json (npm package config), README.md (install and usage guide), .env.example (ANTHROPIC_API_KEY).
Core User Journey
npm install flowdocs -> run npx flowdocs ./exports -> docs and playbook generated in 60 seconds -> share output folder with team -> upgrade to team tier for CI/CD integration.
Architecture Pattern
CLI reads local export folder -> parser extracts node types and edges -> graph builder generates Mermaid dependency map -> Claude API generates per-flow docs and migration playbook -> exporter writes Markdown or Notion-formatted files to output directory.
Data Model
No persistent database in V1 CLI. Inputs: n8n export JSON files. Outputs: Markdown files and Mermaid diagram files written to local output directory.
Integration Points
Claude API for documentation and playbook generation, LemonSqueezy for one-time license payments, Stripe for team SaaS tier, npm registry for distribution.
V1 Scope Boundaries
V1 excludes: web dashboard, team accounts, CI/CD webhook integration, real-time n8n API connection, GUI, cloud hosting of output files.
Success Definition
A paying ops engineer runs FlowDocs on their 50-flow export, hands the output to a new hire, and the new hire understands the entire automation stack without asking the original author a single question.
Challenges
The hardest problem is distribution — CLI tools get zero organic discovery, requiring active posting in n8n-specific communities and subreddits on every update to stay visible.
Avoid These Pitfalls
Do not build a web dashboard before validating that 50+ people pay for the CLI — validate the core output quality first. Do not use your own Claude API key for the CLI at $49 one-time pricing or you will lose money on heavy users. Finding your first 10 paying customers takes longer than building the CLI — post daily in n8n communities for two weeks before expecting organic installs.
Security Requirements
No user auth in V1 CLI. License key validated against LemonSqueezy API on run. Claude API key provided by user via .env — never stored by FlowDocs. Input validation on file paths to prevent directory traversal.
Infrastructure Plan
npm registry for distribution, Vercel static landing page (free tier), LemonSqueezy for license management, no database needed in V1, GitHub Actions for npm publish CI.
Performance Targets
CLI processes 50-flow export in under 90 seconds including Claude API calls, local file I/O under 100ms, no server load targets needed for CLI model.
Go-Live Checklist
- ☐Security audit complete.
- ☐Payment flow tested end-to-end.
- ☐Error tracking via console warnings documented.
- ☐npm package published and installable.
- ☐Custom domain landing page live with SSL.
- ☐Privacy policy and data handling note published.
- ☐3 beta users ran CLI on real exports.
- ☐Rollback plan: previous npm version tagged.
- ☐Launch post drafted for r/n8n and n8n Discord.
First Run Experience
On first run with no arguments: CLI prints a welcome message, shows a sample command with a bundled demo export folder included in the package, and generates demo output files in ./flowdocs-output so users see real output in 10 seconds. No manual config required: demo export included, only ANTHROPIC_API_KEY needed in .env.
How to build it, step by step
1. Define the output schema for flow documentation and migration playbook as TypeScript interfaces in lib/types.ts. 2. Build lib/parser.ts that reads all JSON files in the target directory and extracts node types, trigger conditions, and credential references. 3. Build lib/graph.ts that maps inter-flow dependencies and outputs a Mermaid diagram string. 4. Build lib/claude.ts as an Anthropic SDK wrapper that sends per-flow parsed data and returns structured documentation. 5. Build lib/exporter.ts with Markdown and Notion front-matter output modes. 6. Wire all modules into bin/flowdocs.ts using Commander.js with --output and --format flags. 7. Add a --dry-run flag that shows flow count and estimated Claude API cost before processing. 8. Write README.md with a 3-command quickstart and a before/after screenshot. 9. Publish to npm as flowdocs with a $0 free tier limited to 5 flows and a license key check for unlimited. 10. Run the CLI against a real 20-flow n8n export and verify all output files are readable without editing.
Generated
May 27, 2026
Model
claude-sonnet-4-6
Disclaimer: Ideas on this site are AI-generated and may contain inaccuracies. Revenue estimates, market demand figures, and financial projections are illustrative assumptions only — not financial advice. Do your own research before making any business or investment decisions. Technology availability, pricing, and market conditions change rapidly; always verify details independently.