n8n-node-configuration

Guides operation-aware n8n node configuration with property dependency handling and validation workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Configuring n8n nodes fails when you don't know which fields are required for a given operation or why fields appear and disappear based on other values. This Skill teaches a progressive discovery workflow so you configure nodes correctly in 2-3 validation cycles instead of trial and error. ## Core Features & Use Cases - Operation-Aware Configuration: Explains how resource and operation choices determine required fields, with concrete examples for Slack, HTTP Request, Postgres, IF, Switch, and 15+ other common nodes. - Property Dependency Guidance: Deep reference on the displayOptions mechanism (show/hide rules, AND/OR logic) so you can diagnose why a field is hidden or conditionally required. - Progressive Discovery Workflow: Decision tree for choosing between get_node standard detail, search_properties mode, and full detail, covering 95% of cases with the lightest option. - Use Case: You switch a Slack node from operation "post" to "update" and validation fails. The Skill shows you that update requires messageId instead of channel, and how to verify requirements before reconfiguring. ## Quick Start Ask the AI to help you configure an n8n HTTP Request node that POSTs JSON to an API endpoint, including handling the sendBody dependency.

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 an n8n node with the correct required fields?▼

Start with get_node using standard detail to see required fields and common options for your node type. Configure the minimal fields, validate, then add fields iteratively based on validation errors until the configuration passes.

Why does a required field not appear in my n8n node configuration?▼

Fields in n8n are controlled by displayOptions rules that show or hide them based on other field values. Use get_node with search_properties mode to find what controls the field's visibility, such as setting sendBody to true to reveal the body field.

What is the difference between get_node standard and full detail in n8n?▼

Standard detail returns about 1-2K tokens with required fields and common options, covering roughly 95% of configuration needs. Full detail returns the complete 3-8K token schema with all properties and displayOptions, and should only be used when standard detail is insufficient.

Why does my n8n node configuration break when I change the operation?▼

Different operations on the same node have different required fields. For example, Slack message post requires channel and text, while update requires messageId and text. Always re-check requirements with get_node after switching operations.

How do I avoid SQL injection in n8n Postgres node queries?▼

Use parameterized queries with placeholders like $1 and $2 instead of interpolating expressions directly into the query string. Pass the actual values through the queryParameters field in additionalFields.