n8n-node-configuration

Call get_node with standard detail to see required fields for your chosen resource and operation, then configure only those fields and validate. Different operations require different fields, so re-check requirements whenever you change the operation.

Use standard detail first since it covers about 95% of configuration needs with a small 1-2K token response. Escalate to search_properties mode for specific fields, and reserve full detail (3-8K tokens) only when standard output is insufficient.

Fields disappear because displayOptions rules tie visibility to other field values like resource and operation. Changing operation alters which fields show and which are required, so re-run get_node and validate after any operation change.

The field is hidden by a displayOptions dependency, such as body requiring sendBody=true on the HTTP Request node. Use get_node with search_properties mode to find the controlling field, set it, and the hidden field becomes available.

Use parameterized queries with placeholders like $1 and pass values through additionalFields queryParameters instead of interpolating expressions into the query string. This prevents user input from being executed as SQL.