Node not visible in N8N although logs indicate correct installation

[morliont]

Hi,

Thank you first for creating this node. I am very excited to get this tested.
I tried to install it on my local home server n8n installation through the N8N community nodes interface.
The logs indicate the node correctly being installed and I also see it in the interface.

But when I try to search for it in the workflow view, I cannot seem to find it...
I assume I don't need to build or run any commands (as it probably is happening behind the screens when using the community nodes interface)?

[braidn]

@morliont this should show up in the sidebar after an install. It is definitely odd that you are not seeing it. Will test this locally and see what I can come up with!

[braidn]

@morliont after looking through this, I see the issue!

When installing this package through the community nodes section in the n8n interface, this creates an npm bare repository in your ~/.n8n/nodes directory

This means that if that directory were empty previous to the install, it would now look like (using ls -la):

This means that the ACTUAL module will be in the node_modules/ folder.

Do you have the ability to download this using the manual way outlined in the n8n docs? Afterwards, we could symlink the correct folder to your ~/n8n/nodes folder and you would be OK.

We are currently looking into how this is done by other n8n node community maintainers to see if this is a bug in the way that the package is published and hope to fix it soon.

[morliont]

My apologies for the late answer.

I think I added it manually now to the ~/n8n/nodes folder in my docker container. Is there any extra step I need to do?

[mig5]

I have the same issue. Manual install didn't help, same problem, even after restarting the Docker container. The node type simply doesn't appear in the Nodes panel in a workflow.

Running n8n Version 1.104.2.