Why Aren't My Installed Community Nodes Appearing in n8n?

Based on the troubleshooting documentation for community nodes, it sounds like n8n might not be loading the community nodes because the files aren’t present at startup. Here are some points to consider:

• Persist the Node Files:
  n8n installs community nodes onto the filesystem (typically in the ~/.n8n/nodes directory). If you recreate your container (or, in your case, the podman container), you might lose these installed files. The recommended solution is to persist the ~/.n8n/nodes directory. This way, when n8n starts, it finds all the community node files already in place.

• Environment Variable Option:
  If for some reason you can’t persist the directory, you can set the environment variable N8N_REINSTALL_MISSING_PACKAGES to true. This makes n8n attempt a reinstallation of any missing packages at startup. Note that this might increase startup time and could cause health checks to fail.

Since your settings show that the node is installed but it doesn’t appear when adding a node, it is likely that the node files are not being loaded at startup. Depending on your podman setup, ensure that either you have bound/persisted the directory or configured the environment variable accordingly.

For further details, refer to the troubleshooting guide on the n8n documentation pages concerning missing packages.