Overview
The "Node Inspector" node provides a utility to list and inspect all available n8n nodes. It is particularly useful for users who want to explore the nodes they can use in their workflows, including core, community, and custom nodes. This node helps in discovering what nodes are installed and available, which can assist in workflow design, debugging, or documentation.
A practical example would be using this node to generate a list of all community nodes currently installed, helping a user decide which ones to incorporate into their automation.
Properties
| Name | Meaning |
|---|---|
| Filter | Determines which types of nodes to include in the list: - All Nodes (core, community, and custom) - Community Nodes Only |
Output
The node outputs an array with one item containing a JSON object structured as follows:
nodes: An array of node metadata objects representing the filtered nodes.filter: The filter value used ("all" or "community").totalCount: The total number of nodes returned after filtering.
This output allows downstream nodes or users to programmatically access details about available nodes.
Dependencies
- Requires an API key credential for authentication (referred generically as "an API key credential").
- Internally imports logic from a module named
nodeInspectorLogicto retrieve and filter nodes.
Troubleshooting
- Common issue: Failure to retrieve nodes due to missing or invalid API credentials.
- Error message: "Failed to retrieve nodes: [error message]"
- Resolution: Ensure that the required API key credential is configured correctly in n8n.
- If no nodes appear, verify that the filter property is set correctly and that nodes matching the filter exist.
Links and References
- n8n Documentation – For general information on creating and using nodes.
- No direct external links provided in the source code.