The idea is:
Community node packages should be allowed to define only a credential with an httpRequestNode configuration, without requiring explicitly defined nodes. The current installation process throws an error if the package doesn’t contain standalone node definitions, even though httpRequestNode is intended to auto-generate a usable node from a credential.
My use case:
We’ve built a custom integration that relies entirely on an HTTP Request node generated from a credential. The credential includes a complete httpRequestNode configuration to define its behavior as a node. We published this as a community node package, but installation fails with the error:
Error loading package "[name of package]": The specified package does not contain any nodes
Even though the credential should result in a usable node, the package is rejected.
I think it would be beneficial to add this because:
This would enable developers to create and distribute lightweight HTTP-based integrations using only credentials, which is already supported technically via httpRequestNode. However, the current installation validation blocks this use case. Removing or updating this validation would unlock more modular and simpler node packages in the community ecosystem.
Any resources to support this?
Our package using this approach: GitHub - inmoba/n8n-nodes-inmobalia-crm: Community node for n8n to connect with Inmobalia CRM. Provides OAuth2 authentication and a base HTTP Request node to interact with the Inmobalia CRM API from your workflows.
Are you willing to work on this?
Yes, we’re happy to help provide examples or test changes if needed.