技能 n8n-node-configuration
📦

n8n-node-configuration

安全

Configure n8n Nodes with Operation-Aware Guidance

Struggling with n8n node configuration and property dependencies? Get progressive, operation-aware guidance that reveals required fields based on your specific resource and operation choices.

支援: Claude Codex Code(CC)
🥉 73 青銅
1

下載技能 ZIP

2

在 Claude 中上傳

前往 設定 → 功能 → 技能 → 上傳技能

3

開啟並開始使用

測試它

正在使用「n8n-node-configuration」。 Configure a Slack message update operation

預期結果:

For Slack message updates, you need messageId and text. Unlike the post operation, channel is optional. Example: {resource: message, operation: update, messageId: 123, text: Updated content}

正在使用「n8n-node-configuration」。 Why is my HTTP POST validation failing?

預期結果:

POST requests require sendBody=true, which then requires the body object with contentType and content. Add sendBody: true and a body configuration to pass validation.

安全審計

安全
v1 • 2/25/2026

Static analysis flagged 115 patterns but all are false positives. The skill is documentation-only (SKILL.md) containing educational content about n8n node configuration. Backtick patterns are markdown code formatting, URLs are example endpoints in documentation, and crypto warnings are text pattern matches with no actual cryptographic code. No executable code, network calls, or security risks present.

1
已掃描檔案
797
分析行數
0
發現項
1
審計總數
未發現安全問題
審計者: claude

品質評分

38
架構
100
可維護性
87
內容
50
社群
100
安全
83
規範符合性

你能建構什麼

Workflow Developer Learning n8n

New to n8n and overwhelmed by node configuration options. Get guided explanations of which fields are required for specific operations and why certain fields appear or disappear based on your choices.

Experienced User Exploring New Nodes

Familiar with n8n basics but configuring unfamiliar node types. Use progressive discovery to quickly understand operation-specific requirements without reading full schemas.

Debugging Configuration Errors

Validation errors indicate missing or incorrect fields. Search for specific properties and understand displayOptions rules to fix configuration issues efficiently.

試試這些提示

Basic Node Configuration
I need to configure a Slack node to post messages. What fields are required and what options are available?
Understanding Property Dependencies
Why does the body field disappear when I change my HTTP Request method from POST to GET? Explain the displayOptions rules.
Finding Specific Properties
Use get_node with search_properties mode to find all authentication-related fields for the HTTP Request node.
Complete Configuration Walkthrough
Guide me through configuring an IF node with string comparison conditions. Start with get_node standard detail, validate my configuration, and iterate until valid.

最佳實務

  • Start with get_node using standard detail - it covers 95% of configuration needs with concise responses
  • Validate iteratively after each configuration change - expect 2-3 validation cycles for complex nodes
  • Use search_properties mode when a field seems missing - understand what controls its visibility before adding complexity

避免

  • Over-configuring upfront by adding every possible optional field instead of starting minimal
  • Skipping validation before deploying workflow changes - always validate_node before n8n_update_partial_workflow
  • Assuming configuration transfers between operations - different operations have different required fields

常見問題

What detail level should I use with get_node?
Start with standard detail (the default). It provides required fields and common options in 1-2K tokens. Only use full detail when standard is insufficient for your use case.
Why do fields appear and disappear as I configure?
Fields have displayOptions rules that control visibility based on other field values. For example, body only shows when sendBody=true and method is POST/PUT/PATCH.
How do I find a specific property like authentication headers?
Use get_node with mode: search_properties and propertyQuery: auth. This searches for properties matching your query instead of browsing the full schema.
What is the typical configuration workflow?
1) Identify node type and operation, 2) Get node info with standard detail, 3) Configure required fields, 4) Validate, 5) Fix errors, 6) Repeat until valid, 7) Deploy.
Do different operations need different configurations?
Yes. Resource and operation determine which fields are required. For example, Slack post needs channel and text, but update needs messageId instead of channel.
Should I manually add singleValue for IF node conditions?
No. Auto-sanitization handles operator structure automatically. Focus on business logic and let the system fix singleValue for unary operators like isEmpty.

開發者詳情

檔案結構

📄 SKILL.md