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

n8n-node-configuration

Skill card

combined

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.

Repositories

Other copies

Combined skill

---
name: n8n-node-configuration
description: 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.
---

# n8n Node Configuration

## Prerequisites and Scope
- Use this skill only when the task is to configure an n8n node for a specific resource and operation, not for overall workflow architecture.
- If required inputs, permissions, safety boundaries, or success criteria are missing, stop and ask for clarification.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- If a references/detailed-guide.md file is available in the skill folder, read it before executing and treat its safety, prerequisites, and validation requirements as mandatory.

## Configuration Philosophy
- Start minimal and add complexity as needed (progressive disclosure).
- Most configurations need only standard detail, not the full schema.

## Core Concepts

### Operation-Aware Configuration
- Required fields depend on the resource and operation.
- Example: Slack node operation='post' requires channel and text; operation='update' requires messageId and text but not channel.

### Property Dependencies
- Fields appear or disappear based on other field values via displayOptions.
- Example: HTTP Request node shows sendBody and body only when method='POST'.

### Progressive Discovery
1. get_node({detail: "standard"}) — default; quick overview (~1-2K tokens); covers 95% of needs.
2. get_node({mode: "search_properties", propertyQuery: "..."}) — find specific fields by name.
3. get_node({detail: "full"}) — complete schema (~3-8K tokens); use only when standard is insufficient.

## Configuration Workflow
1. Identify node type and operation.
2. Use get_node with standard detail (default).
3. Configure required fields.
4. Validate configuration.
5. If a field is unclear, use get_node with search_properties mode.
6. Add optional fields as needed.
7. Validate again.
8. Deploy.

## Dynamic Properties
- When standard detail marks a property with dynamicOptions ({methodName, methodType, dependsOn}), its real values come from a live loadOptions/listSearch method, not from bundled docs.
- Do not guess an ID for it.
- Resolve it with n8n_explore_node_resources (requires N8N_MCP_ACCESS_TOKEN, n8n 2.34+).
- All six parameters are required and none are inferred from each other:
  - nodeType: long form (e.g., n8n-nodes-base.googleSheets)
  - version: the node typeVersion the method belongs to
  - methodName: copied verbatim from dynamicOptions
  - methodType: "listSearch" for resource locators, "loadOptions" for plain dropdowns
  - credentialType: e.g., googleSheetsOAuth2Api
  - credentialId: from n8n_manage_credentials({action: "list"})
  - currentNodeParameters: whatever dependsOn names, in its real shape; keep resource-locator values in {__rl: true, mode, value} shape.
- Put the returned value in the config; name is display text only.

## Conflicts
- sickn33/agentic-awesome-skills requires reading references/detailed-guide.md first and treating its safety, prerequisites, and validation as mandatory; czlonkowski/n8n-skills provides the procedure inline without that prerequisite. Follow the combined instruction above, which includes the prerequisite when the file is present and the inline procedure when it is not.