n8n-node-configuration

Diagnose n8n node misconfigurations by interpreting displayOptions and validating fields.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/HustleDanie/n8n-claude-kit --skill n8n-node-configuration-hustledanie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: n8n-node-configuration
Source: https://github.com/HustleDanie/n8n-claude-kit/tree/main/skills/n8n-node-configuration
Command: npx skills add https://github.com/HustleDanie/n8n-claude-kit --skill n8n-node-configuration-hustledanie

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the common frustration of n8n node configuration errors—especially when required fields are hidden or change depending on the selected resource and operation—so you can configure faster and validate correctly instead of trial-and-error.

Core Features & Use Cases

  • Operation-aware required fields: Determines which properties are actually required for the current resource + operation (e.g., Slack post vs update).
  • Property dependency reasoning: Explains how displayOptions visibility rules (show/hide, AND/OR conditions) affect what fields appear in the UI.
  • Progressive discovery workflow: Recommends starting with get_node standard detail, escalating to search_properties when a field is missing, and using detail: "full" only when necessary.
  • Validation-driven iteration: Uses validate_node feedback to guide the next edit and converge to a working configuration efficiently.

Quick Start

Ask: “How do I configure the nodes-base.httpRequest node to make a POST with a JSON body, and which fields become required when I enable sendBody?”

Frequently Asked Questions about n8n-node-configuration

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

FAQPage Schema
Why do n8n node required fields disappear or change when I select a different resource and operation?

n8n node required fields change because displayOptions visibility rules conditionally show or hide properties based on the selected resource and operation. Operation-aware configuration interprets these AND/OR dependency conditions to determine which fields are actually required for your specific setup.

How do I configure n8n nodes when required fields are hidden or missing from the UI?

To configure n8n nodes with hidden fields, start with get_node standard detail, escalate to search_properties to discover missing dependencies, and iterate using validate_node feedback until the node configuration passes validation.

What is the best way to resolve n8n node validation errors for conditional requirements?

The best way to resolve n8n node validation errors is validation-driven iteration: run validate_node, interpret the feedback to identify missing conditional requirements, adjust the configuration, and re-validate until it converges to a valid state.

How does displayOptions dependency logic affect n8n node configuration?

displayOptions dependency logic controls field visibility in n8n nodes using show/hide and AND/OR conditions tied to resource and operation values. Understanding this logic explains why fields appear unexpectedly and guides correct property configuration.

When should I use full detail versus standard detail when inspecting n8n node properties?

Use get_node standard detail first for n8n node inspection, and only escalate to detail: "full" when standard detail is insufficient. If a specific field is still missing, use search_properties to locate hidden properties before resorting to full detail.