n8n-node-configuration

Configure n8n nodes with operation-specific field requirements and property dependencies.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/pessini/aria --skill n8n-node-configuration-pessini
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: n8n-node-configuration
Source: https://github.com/pessini/aria/tree/main/backend/agents/n8n_agent/skills/n8n-node-configuration
Command: npx skills add https://github.com/pessini/aria --skill n8n-node-configuration-pessini

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps users configure n8n nodes efficiently by understanding operation-specific requirements, property dependencies, and common configuration patterns, reducing trial-and-error and configuration time.

Core Features & Use Cases

  • Operation-Aware Configuration: Learn how different operations within a node (e.g., Slack's 'post' vs. 'update') have distinct field requirements.
  • Property Dependency Understanding: Grasp how fields dynamically appear or disappear based on other field values, using the displayOptions mechanism.
  • Progressive Discovery: Master the use of get_node with varying detail levels (standard, full, search_properties) to find the right information efficiently.
  • Common Node Patterns: Quickly learn standard configurations for frequently used nodes like HTTP Request, Slack, IF, and Code.
  • Use Case: A user needs to configure an HTTP Request node to send a POST request with a JSON body. They can use this Skill to understand that sendBody must be true and the body field then becomes required, guided by the Skill's examples and dependency explanations.

Quick Start

Use the n8n-node-configuration skill to understand how to configure the Slack node's 'post message' operation.

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 only appear when another setting is changed?

n8n node fields dynamically appear or disappear using the `displayOptions` mechanism based on other property values. You must set the prerequisite field correctly to trigger the conditional visibility of dependent configuration options.

Why does my n8n HTTP Request node require a body field for a POST request?

The n8n HTTP Request node requires the `sendBody` parameter to be set to `true` for the `body` field to become visible and mandatory. This operation-specific requirement ensures correct payload configuration for POST requests.

What is the best way to find specific property parameters when configuring an n8n node?

Use the `get_node` function with the `search_properties` detail level to find specific n8n node parameters efficiently. This progressive discovery method allows targeted searching without loading the entire node schema.

Do different operations within the same n8n node have distinct field requirements?

Different operations within the same n8n node, such as Slack's 'post' versus 'update', have completely distinct field requirements. Configuring n8n nodes requires understanding these operation-specific parameters to avoid validation errors.

Can I retrieve the full schema of an n8n node to understand all configuration patterns?

Yes, you can retrieve the complete n8n node schema by using the `get_node` function with the `full` detail level. This exposes all available operations and property dependencies for comprehensive node configuration.