n8n-claude-kit

n8n-claude-kit

Zero-to-workflow n8n scaffolding for Claude Code. One-time global install, then /n8n-init in any folder bootstraps a ready-to-build n8n project in under 90 seconds.

What's in the box

• 7 bundled n8n skills — n8n-mcp-tools-expert, n8n-workflow-patterns, n8n-node-configuration, n8n-validation-expert, n8n-expression-syntax, n8n-code-javascript, n8n-code-python
• 3 custom subagents — n8n-workflow-builder, n8n-workflow-validator, n8n-workflow-deployer
• /n8n-init slash command — prompts for project description + n8n credentials, writes CLAUDE.md and .mcp.json, enters plan mode
• No baked-in credentials — every project enters its own n8n URL + API key

Install (once per machine)

/plugin marketplace add HustleDanie/n8n-claude-kit
/plugin install n8n-claude-kit

No credential prompts at install time. The plugin registers subagents, the slash command, and the bundled skills.

Use (per project)

mkdir my-workflow && cd my-workflow
claude

Then in Claude Code:

/n8n-init

It will prompt you for:

1. What this project is for (1-2 sentences)
2. Your n8n instance URL
3. Your n8n API key

And it writes:

• CLAUDE.md — build-loop manual with your project description injected
• .mcp.json — n8n-mcp server configured with your credentials
• .claude/settings.json — default permissions for n8n-mcp tools
• .gitignore — ensures .mcp.json stays out of git

Then it enters plan mode. Describe the workflow you want, fine-tune the plan, approve, build.

Target: active workflow in n8n within 3 minutes of cd.

Why no global credentials?

Many users run multiple n8n instances (personal cloud, client self-hosted, staging, prod). Per-project credentials mean:

• Zero leakage risk across projects
• No secrets in Claude Code's global store
• Switch instances by cding into a different folder

If you want to reuse credentials across projects, copy .mcp.json between folders — but you'll need to do it deliberately.

Subagents

Subagent	When it runs
n8n-workflow-builder	"build me a workflow that..." — orchestrates discover → validate → create → activate
n8n-workflow-validator	"validate this workflow" / "why does this fail" — runs validation profiles, interprets errors
n8n-workflow-deployer	"update this workflow" / "activate X" / "why did this run fail" — handles partial updates, activation, execution diagnosis

Updating

When new n8n skills or subagent improvements ship:

/plugin update n8n-claude-kit

The VERSION.md changelog calls out new skills and behavior changes per release.

Adding your own skills

Bundled skills coexist with skills you install into ~/.claude/skills/. If you need a skill that isn't in the plugin yet, install it locally — the plugin won't conflict. Then open a PR here so everyone gets it in the next release.

Troubleshooting

/mcp doesn't show n8n-mcp after /n8n-init Restart Claude Code. MCP server registration from a newly-written .mcp.json sometimes requires a reload.

"Node not found" when building You're probably using the wrong nodeType prefix. Search/validate tools use nodes-base.slack; workflow tools use n8n-nodes-base.slack. The n8n-mcp-tools-expert skill documents this in detail.

API key rejected Verify the key at <your-n8n-url>/settings/api. Keys tied to a specific user account; make sure the account has workflow permissions.

/n8n-init refuses to overwrite existing files Expected — it asks for confirmation to protect existing work. Say yes if you really want to overwrite.

License

MIT.

Contributing

PRs welcome for new subagents, bundled skills, or slash commands. See VERSION.md for the release process.