n8n-node-configuration

Name: n8n-node-configuration
Author: czlonkowski

5.5kinstalls983forks

How to install n8n-node-configuration?

czlonkowski/n8n-skills/n8n-node-configuration

$npx -y skills add czlonkowski/n8n-skills --skill n8n-node-configuration

Installs into the current project.

Summary

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 p

Files · 1

View on GitHub

SKILL.md

1	# n8n Node Configuration
2
3	Expert 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
11	Configuration 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	"sendBody": true, // Now visible!
66	"body": { // Required when sendBody=true
67	"contentType": "json",
68	"content": {...}
69	}
70	}
71	```
72
73	Mechanism: displayOptions control field visibility
74
75	### 3. Progressive Discovery
76
77	Use the right detail level:
78
79	1. get_node({detail: "standard"}) - DEFAULT
80	- Quick overview (~1-2K tokens)
81	- Required fields + common options
82	- Use first - covers 95% of needs
83
84	2. get_node({mode: "search_properties", propertyQuery: "..."}) (for finding specific fields)
85	- Find properties by name
86	- Use when looking for auth, body, headers, etc.
87
88	3. get_node({detail: "full"}) (complete schema)
89	- All properties (~3-8K tokens)
90	- Use only when standard detail is insufficient
91
92	---
93
94	## Configuration Workflow
95
96	### Standard Process
97
98	1. Identify node type and operation.
99	2. Use `get_node` (standard detail is default).
100	3. Configure required fields.
101	4. Validate configuration.
102	5. If a field is unclear → `get_node({mode: "search_properties"})`.
103	6. Add optional fields as needed.
104	7. Validate again.
105	8. Deploy.
106
107	### Example: Configuring HTTP Request
108
109	The validate-driven loop in practice: start minimal (`method`, `url`, `authentication`), then let each `validate_node` error surface the next required field (`sendBody` for POST → `body` when `sendBody=true`) until valid. Full step-by-step walkthrough in [OPERATION_PATTERNS.md](OPERATION_PATTERNS.md#worked-example-configuring-http-request-step-by-step).
110
111	---
112
113	## get_node Detail Levels
114
115	### Standard Detail (DEFAULT - Use This!)
116
117	✅ Starting configuration
118	```javascript
119	get_node({
120	nodeType: "nodes-base.slack"
121	});
122	// detail="standard" is the default
123	```
124
125	Returns (~1-2K tokens):
126	- Required fields
127	- Common options
128	- Operation list
129	- Metadata
130
131	Use: 95% of configuration needs
132
133	### Full Detail (Use Sparingly)
134
135	✅ When standard isn't enough
136	```javascript
137	get_node({
138	nodeType: "nodes-base.slack",
139	detail: "full"
140	});
141	```
142
143	Returns (~3-8K tokens):
144	- Complete schema
145	- All properties
146	- All nested options
147
148	Warning: Large response, use only when standard insufficient
149
150	### Search Properties Mode
151
152	✅ Looking for specific field
153	```javascript
154	get_node({
155	nodeType: "nodes-base.httpRequest",
156	mode: "search_properties",
157	propertyQuery: "auth"
158	});
159	```
160
161	Use: Find authentication, headers, body fields, etc.
162
163	### Decision Tree
164
165	1. Starting a new node config → `get_node` (standard).
166	2. Standard has what you need → configure with it. Otherwise continue.
167	3. Looking for a specific field → `search_properties` mode. Otherwise continue.
168	4. Still need more → `get_node({detail: "full"})`.
169
170	---
171
172	## Property Dependencies Deep Dive
173
174	Fields have `displayOptions` visibility rules: `show`/`hide` blocks where multiple conditions are AND'd and multiple values are OR'd (e.g. `body` shows when `sendBody=true` AND `method IN (POST, PUT, PATCH)`). The three recurring patterns are the boolean toggle (sendBody → body), the operation switch (post vs update sh

People who liked this also viewed

6 picks

Type

n8n-node-configuration

5.5kinstalls983forks

View on GitHub

How to install n8n-node-configuration?

czlonkowski/n8n-skills/n8n-node-configuration

$npx -y skills add czlonkowski/n8n-skills --skill n8n-node-configuration

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# n8n Node Configuration
2
3	Expert 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
11	Configuration 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	"sendBody": true, // Now visible!
66	"body": { // Required when sendBody=true
67	"contentType": "json",
68	"content": {...}
69	}
70	}
71	```
72
73	Mechanism: displayOptions control field visibility
74
75	### 3. Progressive Discovery
76
77	Use the right detail level:
78
79	1. get_node({detail: "standard"}) - DEFAULT
80	- Quick overview (~1-2K tokens)
81	- Required fields + common options
82	- Use first - covers 95% of needs
83
84	2. get_node({mode: "search_properties", propertyQuery: "..."}) (for finding specific fields)
85	- Find properties by name
86	- Use when looking for auth, body, headers, etc.
87
88	3. get_node({detail: "full"}) (complete schema)
89	- All properties (~3-8K tokens)
90	- Use only when standard detail is insufficient
91
92	---
93
94	## Configuration Workflow
95
96	### Standard Process
97
98	1. Identify node type and operation.
99	2. Use `get_node` (standard detail is default).
100	3. Configure required fields.
101	4. Validate configuration.
102	5. If a field is unclear → `get_node({mode: "search_properties"})`.
103	6. Add optional fields as needed.
104	7. Validate again.
105	8. Deploy.
106
107	### Example: Configuring HTTP Request
108
109	The validate-driven loop in practice: start minimal (`method`, `url`, `authentication`), then let each `validate_node` error surface the next required field (`sendBody` for POST → `body` when `sendBody=true`) until valid. Full step-by-step walkthrough in [OPERATION_PATTERNS.md](OPERATION_PATTERNS.md#worked-example-configuring-http-request-step-by-step).
110
111	---
112
113	## get_node Detail Levels
114
115	### Standard Detail (DEFAULT - Use This!)
116
117	✅ Starting configuration
118	```javascript
119	get_node({
120	nodeType: "nodes-base.slack"
121	});
122	// detail="standard" is the default
123	```
124
125	Returns (~1-2K tokens):
126	- Required fields
127	- Common options
128	- Operation list
129	- Metadata
130
131	Use: 95% of configuration needs
132
133	### Full Detail (Use Sparingly)
134
135	✅ When standard isn't enough
136	```javascript
137	get_node({
138	nodeType: "nodes-base.slack",
139	detail: "full"
140	});
141	```
142
143	Returns (~3-8K tokens):
144	- Complete schema
145	- All properties
146	- All nested options
147
148	Warning: Large response, use only when standard insufficient
149
150	### Search Properties Mode
151
152	✅ Looking for specific field
153	```javascript
154	get_node({
155	nodeType: "nodes-base.httpRequest",
156	mode: "search_properties",
157	propertyQuery: "auth"
158	});
159	```
160
161	Use: Find authentication, headers, body fields, etc.
162
163	### Decision Tree
164
165	1. Starting a new node config → `get_node` (standard).
166	2. Standard has what you need → configure with it. Otherwise continue.
167	3. Looking for a specific field → `search_properties` mode. Otherwise continue.
168	4. Still need more → `get_node({detail: "full"})`.
169
170	---
171
172	## Property Dependencies Deep Dive
173
174	Fields have `displayOptions` visibility rules: `show`/`hide` blocks where multiple conditions are AND'd and multiple values are OR'd (e.g. `body` shows when `sendBody=true` AND `method IN (POST, PUT, PATCH)`). The three recurring patterns are the boolean toggle (sendBody → body), the operation switch (post vs update sh

People who liked this also viewed

6 picks

Type