n8n-node-configuration

Configure n8n nodes with operation-aware property dependency handling.

6|1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/kmshihab7878/claude-code-setup --skill n8n-node-configuration-kmshihab7878
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: n8n-node-configuration
Source: https://github.com/kmshihab7878/claude-code-setup/tree/main/skills/n8n/czlonkowski/skills/n8n-node-configuration
Command: npx skills add https://github.com/kmshihab7878/claude-code-setup --skill n8n-node-configuration-kmshihab7878

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Resolve confusion and errors that arise when n8n node fields appear or disappear, required fields change with operations, and users choose the wrong discovery detail level; this guidance reduces trial-and-error and validation failures when authoring workflows.

Core Features & Use Cases

  • Operation-aware configuration guidance that clarifies which fields are required for a given resource and operation (e.g., Slack post vs update).
  • Property dependency deep dive explaining displayOptions, nested dependencies, and auto-sanitization so hidden-required errors are diagnosed quickly.
  • Progressive discovery workflow showing when to use get_node standard detail, search_properties, and full detail plus validation-driven iteration and common node patterns (HTTP, Webhook, Slack, Postgres, IF, Switch, OpenAI).
  • Real-world example: configure an HTTP Request POST by enabling sendBody, adding a JSON body with contentType=json, and validating until the node passes runtime validation.

Quick Start

Configure an HTTP Request node to POST JSON with sendBody enabled and a JSON body containing name and email.

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 node fields that change based on operation switches?

Configure n8n nodes with operation-aware property dependency handling to manage fields that appear or disappear during operation switches. This approach clarifies which fields are required for a given resource and operation, reducing validation failures during workflow authoring.

Why does my n8n workflow validation fail when sendBody is not enabled?

n8n workflow validation fails when conditional required fields like sendBody are not enabled because displayOptions hide dependent properties. Diagnosing nested dependencies and auto-sanitization rules resolves these hidden-required errors quickly during node configuration.

How do I use get_node to discover n8n node properties and interpret displayOptions?

Use a progressive discovery workflow to choose between get_node standard detail, search_properties, and full detail to find n8n node properties. Interpreting displayOptions reveals nested dependencies and conditional required fields for accurate validation troubleshooting.

What is the best way to set up an HTTP Request node to POST JSON in n8n?

The best way to configure an n8n HTTP Request POST is by enabling sendBody, adding a JSON body with contentType set to json, and iterating with validation until the node passes runtime checks.

Does this n8n configuration guidance work with Slack, Postgres, and AI nodes?

Yes, operation-aware configuration guidance applies to Slack, Postgres, Webhook, IF, Switch, and OpenAI nodes. It clarifies operation-specific required fields and displayOptions dependencies across these common n8n node types.

When should I use full detail versus standard detail for n8n node property discovery?

Use standard get_node detail for common n8n node patterns and switch to full detail or search_properties when resolving complex conditional required fields or validation troubleshooting. This validation-driven iteration reduces trial-and-error during workflow authoring.