n8n-node-configuration

Configure operation-aware n8n nodes with required fields and dependency rules.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Operation-aware node configuration often causes confusion when different operations require different fields, and when options appear or disappear depending on other settings. This skill clarifies how to determine required fields, how to use get_node at different detail levels, and how to reason about property dependencies to avoid validation errors.

Core Features & Use Cases

  • Explains operation-aware configuration and how resource+operation determine requirements.
  • Describes property dependencies and displayOptions to control field visibility.
  • Provides progressive discovery guidance (standard detail, search_properties, full detail) with validation guidance.
  • Includes common patterns and examples for Slack, HTTP, databases, and AI nodes.

Quick Start

Start by calling get_node for the target node with standard detail, then configure the required fields for the chosen operation and validate iteratively.

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 required fields for different operations in n8n nodes?

To configure operation-aware n8n nodes, first call get_node for the target node with standard detail, then configure the required fields for the chosen resource and operation, validating iteratively to ensure correct setup.

Why do n8n node fields disappear or show validation errors when I switch operations?

n8n node fields disappear or trigger validation errors due to property dependencies and displayOptions, which control field visibility based on the selected resource and operation settings, enforcing progressive discovery rules.

How does progressive discovery work when calling get_node for n8n node configuration?

Progressive discovery in get_node works by offering standard, search_properties, and full detail levels, allowing you to incrementally validate required fields and dependency rules for complex n8n nodes without retrieving unnecessary data.

Does operation-aware node configuration apply to Slack, HTTP, and database nodes in n8n?

Yes, operation-aware node configuration applies across Slack, HTTP, database, and AI nodes in n8n, providing common patterns and examples to determine required fields and reason about property dependencies for each specific integration.

What's the best way to avoid validation errors from property dependencies in n8n?

The best way to avoid validation errors from property dependencies in n8n is to reason about displayOptions and use get_node variants to progressively discover and validate required fields for your specific operation.

When should I use full detail instead of standard detail for get_node variants in n8n?

You should use the full detail variant of get_node in n8n when you need complete visibility into all property dependencies and displayOptions to validate complex operation-aware node configurations and troubleshoot dependency issues.