What problem does it solve?
It solves the common frustration of n8n node configuration errors—especially when required fields are hidden or change depending on the selected resource and operation—so you can configure faster and validate correctly instead of trial-and-error.
Core Features & Use Cases
- Operation-aware required fields: Determines which properties are actually required for the current
resource + operation (e.g., Slack post vs update).
- Property dependency reasoning: Explains how
displayOptions visibility rules (show/hide, AND/OR conditions) affect what fields appear in the UI.
- Progressive discovery workflow: Recommends starting with
get_node standard detail, escalating to search_properties when a field is missing, and using detail: "full" only when necessary.
- Validation-driven iteration: Uses
validate_node feedback to guide the next edit and converge to a working configuration efficiently.
Quick Start
Ask: “How do I configure the nodes-base.httpRequest node to make a POST with a JSON body, and which fields become required when I enable sendBody?”