n8n-node-configuration

Fetch live n8n node schemas via get_node_types before configuring nodes.

421|46|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/n8n-io/skills --skill n8n-node-configuration-n8n-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: n8n-node-configuration
Source: https://github.com/n8n-io/skills/tree/main/skills/n8n-node-configuration
Command: npx skills add https://github.com/n8n-io/skills --skill n8n-node-configuration-n8n-io

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents cryptic n8n node validation errors by ensuring you build each node using the exact, version-accurate parameter shape instead of guessing from outdated memory.

Core Features & Use Cases

  • Canonical parameter shaping via get_node_types: forces you to fetch the live node schema using discriminators (resource, operation, and mode where applicable) before composing configuration.
  • Operation-first configuration workflow: guides you to set resource and operation first so conditional fields become available and required fields are not missed.
  • Gotcha-driven references for common node families: includes targeted reference guidance for HTTP, Webhook, Comms, Database, AI Agent node knobs, Switch fallback behavior, and Trigger timing/input shape pitfalls.

Quick Start

Ask the agent: "Configure this n8n node for the goal I describe, but first call get_node_types with the correct discriminators and then build the node config from the returned parameter shape."

Frequently Asked Questions about n8n-node-configuration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure n8n nodes correctly on the first try?

To configure n8n nodes correctly, set the resource and operation first so conditional fields become available. This operation-first workflow ensures required fields are not missed and validates with validate_workflow and post-save inspection via get_workflow_details.

How do conditional parameter dependencies work in n8n workflow validation?

Conditional parameter dependencies in n8n require fetching the live node schema using discriminators like resource, operation, and mode. Respecting these dependencies ensures the correct parameter shape is applied across the workflow lifecycle.

Does this approach work for debugging n8n webhooks and AI agent nodes?

Yes, this approach applies when designing or debugging any n8n node configuration including HTTP, webhooks, databases, comms, triggers, and AI-related nodes. Gotcha-driven references target common pitfalls for these specific node families.

What is the best way to avoid n8n trigger timing and Switch fallback pitfalls?

The best way to avoid n8n trigger timing and Switch fallback pitfalls is using gotcha-driven references that guide operation-first setup. Re-fetching shapes per operation and validating with validate_workflow catches these configuration traps.

Do I need MCP tools to retrieve live n8n node schemas?

Yes, retrieving live n8n node schemas requires calling get_node_types through MCP tools. This enforces canonical parameter shaping by returning the exact parameter shape needed before composing any node configuration.