Grand, all sorted. I just followed the old NPM instructions.
Cheers for maintaining the image, and the support!
For anyone who reads this now, you can use the āinstall community nodesā feature or @digital-boss/n8n-nodes-market node to install this and other custom nodes.
I had wondered what n8n-nodes-market was as the docs was a bit light and the source is not available.
@svenjanssen Is this working with 8.1.x as I canāt seem to get Oath2 to work with credentials.
I can successfully connect with a Postman Collection and get records, and if I do a HTTP request in n8n to get the auth token that works as well.
Through testing, all of these values need to be sent:
But if I try to set up the credentials in n8n that fails as itās missing all for fields.
If i try to pass the token into another http request that is the āsimilarā to the successful Postman request, that fails.
I canāt find at way to pass the token into your module either to call the suite endpoints.
Any ideas?
Simliar problem here as well.
It seems as if this node (and the other community nodes) have been made for SuiteCRM 7 (without the legacy path details)
Yes, this was created for v7. Not having experience with v8 ourselves, we can look at it together. (DM)
I am having trouble getting the n8n-nodes-suitecrm or n8n-nodes-dnc-suitecrm nodes to even try to connect to my server. https (443) is not firewalled and the HTTP Request node will connect ok to my server. I am monitoring connections with tcpdump. All I get when I execute one of the suitecrm nodes is " Problem running workflow Cannot read properties of undefined (reading āreplaceā)". Any ideas anyone. I am very new to n8n and Iām trying to evaluate it for a client. Thanks in advance.
By the way, the Browse console is showing HTTP 500 to the n8n server when I execute the node.
Hey @CommuniG8,
Welcome to the community 
As you are using Community nodes it might be worth opening issues directly with the creators of the nodes.
They never seem to answer and there are people on this chat that seem to understand the nodes.
Hi, try @digital-boss/n8n-nodes-billrun-suitecrm
we cooperate now with the Team of Yonatan (see very top posts) and keep developing their version.
500 indicates that suitecrm has a problem, doesnt it?
OK, Iāll that that node but the 500 errors is not with SuiteCRM itās with n8n. Nothing hits the SuiteCRM Server, monitored it using tcpdump.
Hi Iāve tried the billrun version, still cant connect but I get a more meaningful message on the n8n console. Itās trying to connect to " address: ā::1ā," not the server I have configure in the connection.
It just gets odder! I removed and re-installed the billrun node and its now trying to connect to my server.
Hey @CommuniG8,
The issue wonāt be with n8n directly it will likely be with the node you are using, Typically in the past when I have seen that message with our own nodes the issue is with the response back from the service and it is trying to replace a value on a variable that doesnāt exist. It could also be an issue with the data attempting to be sent as well though.
Another problem Iām having, and this applies to all version of the SuiteCRM plugins, If I install them via the command lineā¦
sudo npm install -g @digital-boss/n8n-nodes-billrun-suitecrm
then I cannot find the node to add when using the n8n UI. If I install them via settings/community node I can add the SuiteCRM node but if I restart n8n the SuiteCRM node is gone again.
Hey @CommuniG8
It is best to install from the ui, I am not sure the node would be removed though how are you running n8n at the moment?
I currently running via an ssh connection and then just running n8n start from the command line
make sure you dont have the same node installed twice, otherwise it can become a problem. Also, with suitecrm there is quite the hickup with making the API available so make sure to read the docs (suitecrm)
Itās not being installed twice, only once and after a restart it has disappeared.
I have now rebuilt the Server using Docker to hold n8n and Iām getting the exact same problem.
The log does contain the followingā¦
n8n detected that some packages are missing. For more information, visit Troubleshooting | n8n Docs