- Home
- Skills
- Czlonkowski
- N8n Skills
- N8n Mcp Tools Expert
n8n-mcp-tools-expert_skill
- Shell
2.2k
GitHub Stars
5
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill czlonkowski/n8n-skills --skill n8n-mcp-tools-expert- README.md2.7 KB
- SEARCH_GUIDE.md8.0 KB
- SKILL.md16.1 KB
- VALIDATION_GUIDE.md9.5 KB
- WORKFLOW_GUIDE.md12.6 KB
Overview
This skill is an expert guide for using the n8n-mcp MCP tools to discover nodes, validate configurations, manage workflows, and deploy templates. It condenses tool selection patterns, parameter formats, and common pitfalls so you can build reliable n8n workflows faster. Use it to choose the right tool, format nodeType correctly, and follow proven iteration patterns.
How this skill works
The skill organizes tools into categories: node discovery, configuration validation, workflow management, and templates. It explains which tools are always available vs. those that require n8n API credentials, how to convert nodeType formats between search/validation and workflow tools, and common operation sequences like search → get_node → validate → update. It also describes validation profiles, detail levels, smart parameters, and auto-sanitization behavior.
When to use it
- Searching for nodes by keyword or capability before building a workflow
- Validating a node or full workflow prior to activation or deployment
- Creating, updating, or iterating on workflows using partial updates
- Deploying a template to an n8n instance or importing real workflow examples
- Troubleshooting configuration errors, version/migration issues, or health checks
Best practices
- Use search_nodes then get_node (detail: standard) for discovery; avoid detail: full unless debugging
- Use the SHORT nodeType format (nodes-base.*) for search/validate tools and FULL format for workflow tools
- Validate with an explicit profile (runtime recommended) and iterate: validate → fix → validate
- Prefer smart parameters (branch, case) when adding connections instead of numeric sourceIndex
- Include intent in n8n_update_partial_workflow calls to get better AI-guided edits
- Rely on templates and validation tools when n8n API tools are unavailable
Example use cases
- Find the Slack node, inspect operations, and copy an example config into a workflow
- Validate a webhook node with profile: runtime, fix missing fields, and revalidate before activating
- Create a new workflow from template, run n8n_deploy_template with autoFix enabled, then validate
- Iteratively build a workflow with n8n_update_partial_workflow using intent for each edit
- Run health checks and tools_documentation to audit tool availability and required credentials
FAQ
Most 'Node not found' errors come from using the wrong nodeType format. Use the SHORT prefix (nodes-base.xxx) for search/validate tools and the FULL prefix (n8n-nodes-base.xxx or @n8n/...) for workflow creation tools.
When should I request get_node with detail: full?
Only when debugging complex issues or needing the complete nested schema. For typical use, detail: standard returns essential operations and properties with much smaller payloads.