n8n GitHub — Repo, Workflows, Contributing

n8n github and github n8n queries surged +30% recently. The audience is split between developers wanting the source code and operators searching for importable workflow JSON. This page covers both.

The official repository

github.com/n8n-io/n8n is the monorepo for the entire platform. Notable directories:

• packages/cli — the runnable n8n server.
• packages/editor-ui — the Vue-based workflow editor.
• packages/nodes-base — the giant collection of built-in integration nodes.
• packages/@n8n/nodes-langchain — AI agent and LangChain nodes.
• docs — source for the docs.n8n.io site.

License: what fair-code actually means

n8n is licensed under the Sustainable Use License — a fair-code license. In practical terms:

• You can read the source, fork it, and self-host for personal or internal business use.
• You can extend it with custom nodes and modify the editor for your team.
• You cannot resell n8n as a hosted automation service competing with n8n Cloud.

For nearly every user this is functionally indistinguishable from open source. The only people who run into the limitation are companies trying to build a Zapier-style competitor on top of n8n's codebase.

Releases and version pinning

Watch the releases page before upgrading production. Major versions occasionally include database migrations or breaking changes to node behavior. Always:

1. Read the release notes for breaking changes.
2. Pin your Docker image tag (e.g. n8nio/n8n:1.79.0, not latest).
3. Test the upgrade on a staging instance with a snapshot of your prod volume.
4. Upgrade prod during a low-traffic window.

Community nodes on GitHub

The community publishes hundreds of additional nodes as npm packages. Discover them by searching GitHub for n8n-nodes-*. Examples worth knowing:

• Vector DB nodes (Qdrant, Pinecone, Weaviate)
• India-specific integrations (Razorpay, Paytm, Karix SMS)
• Niche scrapers and CRM connectors

Community nodes work on self-host. They are limited or unavailable on n8n Cloud — another point in favor of self-hosting for heavy customization.

The "n8n workflow github" pattern

Many teams keep workflow JSON in a Git repository:

1. Build and test a workflow in n8n's editor.
2. Export as JSON.
3. Strip credentials and commit to a private repo.
4. CI deploys to staging n8n via the n8n API on merge.
5. Tag releases for promotion to prod.

This is the same pattern that gave rise to "workflow github" searches. If you don't want to roll your own repo, our curated library serves the same purpose for common use cases.

Issues and bug reports

Before filing an issue on the n8n repo, check:

• You are on the latest minor version.
• The bug is reproducible with credentials stripped (so maintainers can reproduce).
• An existing issue does not already cover it.

Good bug reports include n8n version, Node version, Docker tag, full stack trace, and a minimal workflow JSON that reproduces the issue.

Curated free workflows