What problem does it solve?
Configuring n8n nodes is often hard because each operation imposes different required fields and visibility rules. This skill provides a structured approach to understand and apply operation-specific requirements, property dependencies, and recommended discovery tools.
Core Features & Use Cases
- Operation-aware configuration: Understand how resource + operation determine required fields across common nodes like Slack, HTTP, Postgres, and Gmail.
- Property dependencies and displayOptions: Learn how fields appear or disappear based on other values to build robust configurations.
- Progressive discovery workflow: Start with get_node essentials, then use get_node(mode: "search_properties"), and resort to get_node(detail: "full") only when necessary.
- Validation-guided iterations: Validate after changes and use dependency hints to fix issues quickly.
- Common patterns by node type: Apply recurring templates for HTTP, Slack, database, and AI nodes.
- Use cases include new node configuration, debugging missing required fields, and handling operation changes.
Quick Start
Start by retrieving essentials for a node type (e.g., nodes-base.slack) with get_node to view supported operations and required fields. Then configure a minimal example for the chosen operation (for Slack post, provide resource, operation, channel, and text), run validation, and progressively add dependencies as needed. If validation indicates missing dependencies, switch to get_node({mode: "search_properties", propertyQuery: "body"}) to reveal controls, then re-validate. When changing operations, re-check requirements with get_node for the new operation to ensure a valid configuration.
