Custom Node approval

Questions
,
1

Describe the problem/error/question

I submitted the node for approval to be included in n8n Cloud, but it was rejected due to having dependencies listed in package.json.When reviewing other community nodes, I noticed they do include dependencies—so I’m confused:

  • Are custom nodes not allowed to have any dependencies at all?
  • Or are only certain types of dependencies restricted?
  • Does this mean a node like mine cannot be approved for n8n Cloud?
  • Could this restriction also be related to the workflow error I mentioned above?

Information on your n8n setup

  • n8n version: 1.93.0
2

Hey @Itay_Explorium, welcome to the forum! :raised_hands:

We are in the process of enabling a subset of community nodes on n8n cloud. We call these ‘verified nodes’ and they have to go through verification by n8n. These nodes are in fact not allowed to have any external dependencies for now.

But that’s just if you want a community node to be verified and available on n8n cloud. You can still build the node and publish to npm for use on self-hosted instances.

We have some things in the docs that should help clarify it:

Maybe there’s a way to remove the dependencies from your node? Most nodes, esp. for integrations, should actually work without external dependencies and as declarative-style nodes.

I also want to call out that we are working to enable external dependencies on cloud eventually, so this restriction might not exist forever. But for now, the limitation exists.

Let me know if you have further questions! :v:

3 Likes