n8n-node-configuration

1# n8n Node Configuration
2 
3Expert guidance for operation-aware node configuration with property dependencies.
4 
5---
6 
7## Configuration Philosophy
8 
9**Progressive disclosure**: Start minimal, add complexity as needed
10 
11Configuration best practices:
12- `get_node` with `detail: "standard"` is the most used discovery pattern
13- 56 seconds average between configuration edits
14- Covers 95% of use cases with 1-2K tokens response
15 
16**Key insight**: Most configurations need only standard detail, not full schema!
17 
18---
19 
20## Core Concepts
21 
22### 1. Operation-Aware Configuration
23 
24**Not all fields are always required** - it depends on operation!
25 
26**Example**: Slack node
27```javascript
28// For operation='post'
29{
30  "resource": "message",
31  "operation": "post",
32  "channel": "#general",  // Required for post
33  "text": "Hello!"        // Required for post
34}
35 
36// For operation='update'
37{
38  "resource": "message",
39  "operation": "update",
40  "messageId": "123",     // Required for update (different!)
41  "text": "Updated!"      // Required for update
42  // channel NOT required for update
43}
44```
45 
46**Key**: Resource + operation determine which fields are required!
47 
48### 2. Property Dependencies
49 
50**Fields appear/disappear based on other field values**
51 
52**Example**: HTTP Request node
53```javascript
54// When method='GET'
55{
56  "method": "GET",
57  "url": "https://api.example.com"
58  // sendBody not shown (GET doesn't have body)
59}
60 
61// When method='POST'
62{
63  "method": "POST",
64  "url": "https://api.example.com",
65…