N8N Node Configuration

# n8n Node Configuration

Expert guidance for operation-aware node configuration with property dependencies.

When to Use This Skill

Use this skill when:

- Configuring n8n nodes

- Understanding property dependencies

- Determining required fields

- Choosing between get_node detail levels

- Learning common configuration patterns by node type

---

Configuration Philosophy

**Progressive disclosure**: Start minimal, add complexity as needed

Configuration best practices:

- `get_node` with `detail: "standard"` is the most used discovery pattern

- 56 seconds average between configuration edits

- Covers 95% of use cases with 1-2K tokens response

**Key insight**: Most configurations need only standard detail, not full schema!

---

Core Concepts

1. Operation-Aware Configuration

**Not all fields are always required** - it depends on operation!

**Example**: Slack node

// For operation='post'
{
  "resource": "message",
  "operation": "post",
  "channel": "#general",  // Required for post
  "text": "Hello!"        // Required for post
}

// For operation='update'
{
  "resource": "message",
  "operation": "update",
  "messageId": "123",     // Required for update (different!)
  "text": "Updated!"      // Required for update
  // channel NOT required for update
}

**Key**: Resource + operation determine which fields are required!

2. Property Dependencies

**Fields appear/disappear based on other field values**

**Example**: HTTP Request node

// When method='GET'
{
  "method": "GET",
  "url": "https://api.example.com"
  // sendBody not shown (GET doesn't have body)
}

// When method='POST'
{
  "method": "POST",
  "url": "https://api.example.com",
  "sendBody": true,       // Now visible!
  "body": {               // Required when sendBody=true
    "contentType": "json",
    "content": {...}
  }
}

**Mechanism**: displayOptions control field visibility

3. Progressive Discovery

**Use the right detail level**:

1. **get_node({detail: "standard"})** - DEFAULT

- Quick overview (~1-2K tokens)

- Required fields + common options

- **Use first** - covers 95% of needs

2. **get_node({mode: "search_properties", propertyQuery: "..."})** (for finding specific fields)

- Find properties by name

- Use when looking for auth, body, headers, etc.

3. **get_node({detail: "full"})** (complete schema)

- All properties (~3-8K tokens)

- Use only when standard detail is insufficient

---

Configuration Workflow

Standard Process

1. Identify node type and operation
   ↓
2. Use get_node (standard detail is default)
   ↓
3. Configure required fields
   ↓
4. Validate configuration
   ↓
5. If field unclear → get_node({mode: "search_properties"})
   ↓
6. Add optional fields as needed
   ↓
7. Validate again
   ↓
8. Deploy

Example: Configuring HTTP Request

**Step 1**: Identify what you need

// Goal: POST JSON to API

**Step 2**: Get node info

const info = get_node({
  nodeType: "nodes-base.httpRequest"
});

// Returns: method, url, sendBody, body, authentication required/optional

**Step 3**: Minimal config

{
  "method": "POST",
  "url": "https://api.example.com/create",
  "authentication": "none"
}

**Step 4**: Validate

validate_node({
  nodeType: "nodes-base.httpRequest",
  config,
  profile: "runtime"
});
// → Error: "sendBody required for POST"

**Step 5**: Add required field

{
  "method": "POST",
  "url": "https://api.example.com/create",
  "authentication": "none",
  "sendBody": true
}

**Step 6**: Validate again

validate_node({...});
// → Error: "body required when sendBody=true"

**Step 7**: Complete configuration

{
  "method": "POST",
  "url": "https://api.example.com/create",
  "authentication": "none",
  "sendBody": true,
  "body": {
    "contentType": "json",
    "content": {
      "name": "={{$json.name}}",
      "email": "={{$json.em