n8n-node-configuration

Guides operation-aware n8n node configuration using property dependencies and progressive schema discovery.

Updated Aug 3, 2026
One-click install
npx skills add https://github.com/alvarocubacc/n8n-workflow-builder --skill n8n-node-configuration-alvarocubacc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: n8n-node-configuration
Source: https://github.com/alvarocubacc/n8n-workflow-builder/tree/main/n8n-skills/skills/n8n-node-configuration
Command: npx skills add https://github.com/alvarocubacc/n8n-workflow-builder --skill n8n-node-configuration-alvarocubacc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Configuring n8n nodes is error-prone because required fields change per operation and fields appear or disappear based on displayOptions dependencies, causing confusing validation failures. ## Core Features & Use Cases - Operation-Aware Configuration: Explains how resource and operation choices determine required fields, with examples for Slack, HTTP Request, Postgres, IF, and more. - Property Dependency Guidance: Teaches the displayOptions show/hide mechanism, AND/OR condition logic, and how to troubleshoot fields that are required but not visible. - Progressive Discovery Workflow: Directs use of get_node with standard detail first, search_properties mode when stuck, and full detail only when necessary. - Use Case: When a POST request validation fails with "body required", use this Skill to learn that sendBody must be true first, then configure the body content structure correctly. ## Quick Start Ask the AI to configure an n8n HTTP Request node that POSTs JSON to an API endpoint and explain which fields are required.

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 when required fields change per operation?

Call get_node with standard detail to see operation-specific requirements, then configure only the required fields for your chosen resource and operation. Different operations like Slack post versus update require different fields, so re-check requirements whenever you switch operations.

When should I use get_node standard detail versus full detail in n8n?

Start with standard detail, which covers about 95% of configuration needs in a small response. Escalate to search_properties mode to find specific fields, and use full detail only when the standard schema is insufficient.

Why is an n8n field required but not visible in my configuration?

The field is controlled by displayOptions dependencies, meaning it only appears when other fields hold specific values. For example, the HTTP Request body field requires sendBody set to true and a POST, PUT, or PATCH method before it becomes visible and required.

How do n8n displayOptions show and hide rules work?

displayOptions show a field when all listed conditions match, with multiple values in one condition treated as OR logic. Hide rules do the opposite, removing fields when conditions match, such as hiding the body field for GET requests.

Does n8n auto-sanitization fix missing required fields?

No, auto-sanitization only fixes operator structure issues like adding singleValue for unary IF operators such as isEmpty. You must add missing required fields like channel or messageId yourself based on the operation requirements.