Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Use when building or editing any AI feature in n8n: AI Agents, Text Classifier, Information Extractor, Sentiment Analysis, Summarization Chain, Basic LLM Chain, embeddings, vector stores, single one-shot LLM calls, or AI media generation (image / audio / video) via the native LangChain provider nodes. Triggers on any `@n8n/n8n-nodes-langchain.*` node, "agent", "chat assistant", "LLM with tools", "tool calling", "fromAi", "system prompt", "memory window", "structured output", "outputParser", "function calling", "RAG", "vector store", "embeddings", "classify with AI", "extract fields with LLM", "sentiment analysis", "summarize with LLM", "single LLM call", chat triggers with files, AI image / video / audio generation, or any multi-turn or one-shot LLM behavior.
Use when handling files, images, attachments, or binary data in n8n, OR when an AI agent needs to take a user-uploaded file as tool input or return a generated file. For Data Tables (schemas, dedup, persistent state), see the separate n8n-data-tables skill. Triggers on "file", "image", "PDF", "attachment", "binary", "upload", "download", chat trigger with files, agent tool that needs a file, vision/multimodal, or any handling of non-JSON file data.
Use when the user reaches for a Code node, mentions writing JavaScript or Python in n8n, or any custom logic comes up in workflow design. Triggers on "Code node", "Code", "JavaScript", "Python", "custom logic", "transform data", "$input", "$json transformation", "loop in code", "write a function", or any time the obvious answer seems to be "just put it in code."
Use when writing or reviewing n8n SDK code that wires IF, Switch, Merge, error outputs, or any multi-input/multi-output connection. Triggers on .add(), .to(), .input(n), .output(n), .onTrue, .onFalse, .onCase, .onError, useDataOfInput, merge, switch, IF nodes, error branches, fan-out, fan-in, or any review of the workflow's connections object.
Use when handling any auth, API keys, tokens, OAuth, bearer tokens, basic auth, or secret values in n8n workflows. Triggers on "API key", "token", "bearer", "OAuth", "secret", "auth", "credentials", "Authorization header", "x-api-key", or any node configuration that mentions a third-party service.
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Expert skills for building n8n workflows with n8n-mcp
n8n workflow automation integration
Claude Code plugin for n8n-as-code. Adds the n8n-architect skill and uses the n8nac CLI as its local knowledge/runtime bridge.
Use this agent when you need to design, build, or validate n8n automation workflows. This agent specializes in creating efficient n8n workflows using proper validation techniques and MCP tools integration.\n\nExamples:\n- <example>\n Context: User wants to create a Slack notification workflow when a new GitHub issue is created.\n user: "I need to create an n8n workflow that sends a Slack message whenever a new GitHub issue is opened"\n assistant: "I'll use the n8n-workflow-builder agent to design and build this GitHub-to-Slack automation workflow with proper validation."\n <commentary>\n The user needs n8n workflow creation, so use the n8n-workflow-builder agent to handle the complete workflow design, validation, and deployment process.\n </commentary>\n</example>\n- <example>\n Context: User has an existing n8n workflow that needs debugging and optimization.\n user: "My n8n workflow keeps failing at the HTTP Request node, can you help me fix it?"\n assistant: "I'll use the n8n-workflow-builder agent to analyze and debug your workflow, focusing on the HTTP Request node configuration."\n <commentary>\n Since this involves n8n workflow troubleshooting and validation, use the n8n-workflow-builder agent to diagnose and fix the issue.\n </commentary>\n</example>\n- <example>\n Context: User wants to understand n8n best practices and available nodes for a specific use case.\n user: "What are the best n8n nodes for processing CSV data and sending email reports?"\n assistant: "I'll use the n8n-workflow-builder agent to explore the available nodes and recommend the best approach for CSV processing and email automation."\n <commentary>\n This requires n8n expertise and node discovery, so use the n8n-workflow-builder agent to provide comprehensive guidance.\n </commentary>\n</example>
Design complex n8n workflows with AI assistance - loops, branching, error handling
Generate n8n automation workflows from natural language descriptions
n8n's MCP makes the connection. n8n Skills set the standard.
Built by the n8n team to pair with n8n's instance-level MCP server. Your coding agent can now build and edit workflows through the MCP, and the skills enable it to get it right the first time.
What's inside:
An n8n instance (any plan, Cloud or self-hosted) with the instance-level MCP server enabled. See n8n's MCP setup guide.
Pick your platform:
Inside Claude Code, run these one at a time:
/plugin marketplace add n8n-io/skills
/plugin install n8n-skills@n8n-io
Restart Claude Code. Skills load automatically.
Each coding agent has its own skill format. Follow your platform's docs for installing skills
skills.sh handles a few popular platforms via npx. From your project folder:
npx skills add n8n-io/skills
Compatibility varies by agent. Check skills.sh for support on your specific platform.
AGENTS.mdThis project uses n8n. When working with workflows, nodes, expressions, or
the n8n MCP tools, always start by loading the `using-n8n-skills` meta-skill
and follow its routing into the matching capability skill before acting.
The plugins ship a SessionStart hook that loads the entry-point skill for you. Plain skill installs don't have that hook, so the snippet is what cues your agent to start every n8n task by loading
using-n8n-skills.
| Skill | When it activates |
|---|---|
n8n-workflow-lifecycle | Starting, designing, organizing, or finishing a workflow |
n8n-subworkflows | Anything reusable, multi-step builds |
n8n-extending-mcp | Need capabilities the MCP doesn't have |
n8n-expressions | Writing {{}}, $json, $node |
n8n-node-configuration | Configuring any node |
n8n-code-nodes | Custom logic, Code node consideration |
n8n-connections | IF/Switch/Merge wiring, multi-IO |
n8n-loops | Loops, batching, paginated APIs |
n8n-agents | LangChain Agent node, tools, system prompts, structured output |
n8n-error-handling | Webhook APIs, production workflows |
n8n-credentials-and-security | Auth, API keys, tokens |
n8n-binary-and-data | Files, images, attachments, vision |
n8n-data-tables | Data Tables: schemas, dedup, persistent state |
n8n-debugging | Things break |
A 15th meta-skill, using-n8n-skills, is loaded by the SessionStart hook in plugins and routes your agent to the right capability skill on every n8n task.
Each skill is a markdown file. Frontmatter tells the agent when to load it. The SessionStart hook routes to the right one on every n8n task; PreToolUse hooks pull the matching skill back into context before high-impact MCP calls. It's all just markdown. Disagree with a call? Fork it.
See CLAUDE.md, the contributing guide for humans and AI agents alike. Open an issue first. We don't accept PRs that haven't been discussed in an issue.
Looking for contributors: feature parity plugins for other coding agents (Cursor, Codex, OpenCode, etc.). The skills are just markdown, the work is wrapping them so they activate in those harnesses the way they do in Claude Code.
Apache 2.0. See LICENSE.