The things is, this node i am building is for my own website/service, means my users should be able to select the integration that i have created.
According to docs i have to publish the node to npm, and give for verification to n8n team but if i give to npm then wouldn’t my node’s code will be publicly available? How will i keep it private. I think i am missing something while reading the docs. I genuinely don’t know the process for publishing. Like there is slack which has its own integration, like that i have made for my website/service.
What is the error message (if any)?
-NA
Please share your workflow
-NA
(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
It sounds like you want it to be verified for cloud users. See the requirements for that here
A requirement is to have your node be MIT licenced. Which means the code has to be open and gives permission for anyone to use the code for any reason.
Many of us using n8n also will not use a custom node unless we can read the code first since it is a huge security risk using non-verified code.
It is only the node code that will be available though, and “glue code” like the code written in nodes, especially the declarative mode, is not really worth anything. You don’t have to be worried about people stealing anything (unless your API has " security through obscurity" but then you have a different set of issues.
If you really want to keep it private, then you need to install it into a custom docker image and distribute that to your users. Of course that can only be used to self-hosted. To see the docs for that here
My main goal is that my integration should appear on this page (Best apps & software integrations | n8n) when someone search about it.
and also while creating workflow if someone search for my service, it should be listed like in image.
Any node that you find in the product has its code available, the source for n8n is available and the same applies to any community that is verified.
If you want to keep your node private you don’t need to publish it to npm but that does also mean you can’t get it verified.
Verified nodes also get a spot on our website so users can find them as well, the one you found previously isn’t for a complete integration it says you need to use the http request node but it can work.
if i publish my node on npm which will be public and give to n8n for verification and then if it is verified, it automatically listed on Best apps & software integrations | n8n and users can use it to create workflow, right?
Also other quesiton i have is, i am able to see verified checkmark next to some integrations like in the image
how can i get this verified checkmark for my integration, beacause the node i am building is for my website/service only. so it is officially getting created by my service only and not by 3rd party.
