n8n Node Configuration is a skill for Claude that covers how to set up node parameters in n8n workflows. Which fields a node needs depends on its resource and operation, and fields appear or vanish through displayOptions rules, so the skill teaches Claude to start minimal and let validation show what is missing.
It covers the get_node detail levels, resolving dynamic dropdown values, patterns for resource, HTTP, database and conditional nodes, surgical edits with patchNodeField, settings for the native nodes that replace Code, and misconfigurations that pass validation but misbehave at runtime.
What You Get
- A decision tree for get_node standard, search_properties and full detail
- An explanation of operation-aware requirements, with Slack post versus update as the example
- How displayOptions show and hide fields, with HTTP Request sendBody and body as the example
- Patterns for resource and operation nodes, HTTP nodes, database nodes and IF, Switch and Merge nodes
- Traps for Summarize, Split Out, Merge, Compare Datasets, Remove Duplicates, Date and Time, HTTP pagination and Crypto
- Silent failures: Switch without a fallback output, Merge input counts, SQL built from interpolation, Slack Block Kit wrapping and the Respond to Webhook code default
Common Use Cases
- Configuring a Slack, Google Sheets or Airtable node for a specific operation
- Finding which field makes a hidden property appear
- Resolving a Google Sheets tab or Slack channel value from a live dropdown
- Replacing a Code node with a Summarize, Merge or Remove Duplicates node
- Editing one line of a Code node without resending the whole field
What Makes It Unique
It focuses on how n8n node parameters behave: required fields depend on the operation and visibility depends on other fields. It gives configurations and traps for the native nodes that replace Code, and a list of misconfigurations that validate cleanly. It also warns against placeholder credential IDs and non-UUID node ids, which break the n8n editor.
Under The Hood
The skill is instructions and four reference markdown files, with no scripts. It tells Claude to read node definitions, search node properties and validate configuration through the n8n-mcp tools, and to patch workflows on your n8n server with partial updates. For dynamic dropdowns it calls a tool that uses a credential stored in your n8n instance to look up live values such as channels or sheet tabs from the connected service.