n8n-node-configuration

Configure n8n node fields based on resource and operation dependencies.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/erlebach/gordon --skill n8n-node-configuration-erlebach
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: n8n-node-configuration
Source: https://github.com/erlebach/gordon/tree/main/skills/agent_skills/n8n-node-configuration
Command: npx skills add https://github.com/erlebach/gordon --skill n8n-node-configuration-erlebach

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Operation-aware configuration for n8n nodes clarifies which fields are required for each resource-and-operation combination, reducing validation errors and guesswork.

Core Features & Use Cases

  • Operation-aware configuration: resource + operation determine required fields.
  • Property dependencies: displayOptions control visibility to show/hide fields based on other values.
  • Progressive discovery: use get_node (standard), get_node({mode: 'search_properties'}), and get_node({detail: 'full'}) to identify needs; validate iteratively.
  • Real-world use cases: Slack post vs update, HTTP POST with body, database queries.

Quick Start

Start with a minimal node configuration for your target operation, then validate and expand based on dependency hints.

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 n8n node operations without validation errors?

Operation-aware configuration for n8n nodes clarifies which fields are required for each resource-and-operation combination, reducing validation errors and guesswork by enforcing operation context and property dependencies.

How do displayOptions work for showing or hiding fields in n8n node configuration?

n8n displayOptions control field visibility by showing or hiding properties based on other values within the node configuration, ensuring users only see fields relevant to their selected resource and operation combination.

What is the best way to discover required properties when setting up complex n8n nodes?

Progressive discovery uses get_node in standard mode, then get_node with search_properties mode and full detail, to identify required fields iteratively and validate node configuration step by step.

Can I use this operation-aware configuration approach for Slack, HTTP, and database nodes in n8n?

Yes, operation-aware configuration applies to configuring Slack post versus update operations, HTTP POST requests with body payloads, database queries, and conditional nodes by guiding users through dependencies and discovery workflows.

Why does my n8n node configuration fail validation when switching between operations?

n8n node configuration fails validation when required fields for the selected resource and operation combination are missing, because displayOptions enforce operation context and property dependencies that must be satisfied before execution.