n8n-node-configuration

Start with get_node_essentials for the node type, which returns required fields and common options with a 91.7% success rate. Configure the minimal fields, validate, then iterate based on validation errors, typically resolving within 2-3 cycles.

Use get_node_essentials first since it covers about 90% of configuration needs and is faster. Escalate to get_property_dependencies when field visibility is unclear, and only use get_node_info when you need the complete schema with all properties.

Fields are controlled by displayOptions rules tied to resource and operation values, so switching operations changes which fields are visible and required. For example, Slack's post operation requires channel while update requires messageId instead.

The field is hidden by displayOptions until its dependency conditions are met, such as HTTP Request's body field requiring sendBody=true and a POST/PUT/PATCH method. Use get_property_dependencies to reveal the exact conditions controlling visibility.

Common gotchas include forgetting sendBody:true for POST requests, accessing webhook data at $json instead of $json.body, omitting the # prefix for Slack channels, using string interpolation instead of parameterized SQL queries, and leaving schedule triggers without an explicit timezone.