What problem does it solve?
Resolve confusion and errors that arise when n8n node fields appear or disappear, required fields change with operations, and users choose the wrong discovery detail level; this guidance reduces trial-and-error and validation failures when authoring workflows.
Core Features & Use Cases
- Operation-aware configuration guidance that clarifies which fields are required for a given resource and operation (e.g., Slack post vs update).
- Property dependency deep dive explaining displayOptions, nested dependencies, and auto-sanitization so hidden-required errors are diagnosed quickly.
- Progressive discovery workflow showing when to use get_node standard detail, search_properties, and full detail plus validation-driven iteration and common node patterns (HTTP, Webhook, Slack, Postgres, IF, Switch, OpenAI).
- Real-world example: configure an HTTP Request POST by enabling sendBody, adding a JSON body with contentType=json, and validating until the node passes runtime validation.
Quick Start
Configure an HTTP Request node to POST JSON with sendBody enabled and a JSON body containing name and email.