domains / families / agent-tooling / n8n-node-configuration

n8n-node-configuration

combined

Operation-aware node configuration guidance. Use when configuring nodes, understanding property dependencies, determining required fields, choosing between get_node detail levels, or learning common configuration patterns by node type. Always use this skill when setting up node parameters — it explains which fields are required for each operation, how displayOptions control field visibility, and when to use patchNodeField for surgical edits vs full node updates. Operation-aware node configuration guidance. Use when configuring nodes, understanding property dependencies, determining required fields, choosing between get_node detail levels, or learning common configuration patterns by node type.

When to use

• You need to configure an n8n node correctly for a specific resource and operation.
• The task involves required fields, property dependencies, or choosing the right `get_node` detail level.
• You are troubleshooting node setup rather than overall workflow architecture.

When not to use

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The first copy is the substantive procedure: it defines the operation-aware configuration model, the get_node detail-level decision tree, the displayOptions mechanism, and the dynamic-properties resolution workflow using n8n_explore_node_resources. The second copy is a thin wrapper that defers to a references/detailed-guide.md file and adds generic safety and scope-limitation language, but it does not contain the actual steps. Because the second copy introduces mandatory constraints (read the detailed guide first, treat its safety/prerequisites/validation as mandatory, stop for clarification when inputs are missing) that the first copy does not state, crowning the first copy would hide a real alternative workflow. The copies overlap in purpose but each has material content the other lacks.