n8n-node-configuration

Guides operation-aware n8n node configuration using property dependencies and progressive discovery.

2|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/mdc159/cbass --skill n8n-node-configuration-mdc159
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: n8n-node-configuration
Source: https://github.com/mdc159/cbass/tree/main/.claude/skills/n8n-node-configuration-v1.0.0
Command: npx skills add https://github.com/mdc159/cbass --skill n8n-node-configuration-mdc159

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Configuring n8n nodes is error-prone because required fields change per operation and fields appear or disappear based on displayOptions dependencies, causing confusing validation failures. ## Core Features & Use Cases - Progressive Discovery Workflow: Start with get_node_essentials (91.7% success rate), escalate to get_property_dependencies or get_node_info only when needed. - Dependency Awareness: Explains displayOptions show/hide rules, AND/OR condition logic, and conditional required fields like HTTP Request's sendBody/body chain. - Operation Patterns Library: Ready-made minimal configurations for 20+ popular nodes including HTTP Request, Webhook, Slack, Gmail, Postgres, Set, Code, IF, Switch, OpenAI, and Schedule Trigger. - Use Case: When a Slack node validation fails after switching from post to update operation, use this Skill to identify that messageId is now required and channel became optional. ## Quick Start Ask the AI to configure an n8n HTTP Request node that POSTs JSON to an API endpoint and explain which fields are required.

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 an n8n node with required fields?▼

Start with get_node_essentials to get required fields and common options for the node type, then configure minimally and validate iteratively. This essentials-first approach succeeds 91.7% of the time without needing the full schema.

get_node_essentials vs get_node_info in n8n, which should I use?▼

Use get_node_essentials first since it covers about 90% of configuration needs with faster results. Escalate to get_property_dependencies for visibility rules, and only use get_node_info when you need the complete schema with all properties.

Why does an n8n field disappear when I change the operation?▼

Fields disappear because displayOptions rules tie visibility to resource and operation values. Different operations require different fields, so re-check get_node_essentials after switching operations to see the new requirements.

Why does n8n validation say a field is required but I cannot see it?▼

The field is hidden by a displayOptions dependency, such as body requiring sendBody=true on the HTTP Request node. Call get_property_dependencies to find which controlling field value makes it visible and required.

How do binary and unary operators differ in n8n IF nodes?▼

Binary operators like equals and contains require both value1 and value2, while unary operators like isEmpty and isNotEmpty need only value1 plus singleValue set to true. Auto-sanitization adds singleValue automatically on save.