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.
スキルZIPをダウンロード
Claudeでアップロード
設定 → 機能 → スキル → スキルをアップロードへ移動
オンにして利用開始
テストする
「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.
セキュリティ監査
安全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.
品質スコア
作れるもの
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.
これらのプロンプトを試す
I need to configure a Slack node to post messages. What fields are required and what options are available?
Why does the body field disappear when I change my HTTP Request method from POST to GET? Explain the displayOptions rules.
Use get_node with search_properties mode to find all authentication-related fields for the HTTP Request node.
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