a month ago
I created a workflow in n8n that works fine, but the main problem occurs when I try to connect to Chatwoot — it just doesn’t work anymore. Previously, it worked very well, but now it stopped working. I tested the connection to the Chatwoot API from my local command line, and it works, so I assume the issue is with the connection between n8n and Chatwoot. Also, I tested reaching Google from inside n8n and it works perfectly fine. Could there be a firewall or network setting that needs to be checked?
I also checked the logs, and Chatwoot doesn’t even receive the request. Meanwhile, n8n reports that it couldn’t reach Chatwoot, and the process stops due to a timeout.
9 Replies
a month ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open brody • about 1 month ago
a month ago
Ouch, that n8n and chatwoot integration also consumed me for weeks.
There could be a myriad of things. Maybe you're just using a variable in n8n that isn't encoded properly. Can you share the cURL here (hide sensitive info)?
Also, what chatwoot version are you using? and is it cloud or self-hosted?
a month ago
N8N Version: 1.91.3 (Self Hosted)
Chatwoot Version: v4.1.0 (Self Hosted)
Issue:
When I run this curl command in my terminal, it works perfectly:
Copiar
curl -v -H "api_access_token: FFFFFFFFFF" https://mydomain.com/api/v1/accounts/1/conversations/109/messages
However, when I try to do the same request inside n8n, it fails.
This problem only happens with that specific domain. For example, if I test a GET request to Google from n8n, it works fine with no issues.
a month ago
The request begins but never completes and eventually times out.
a month ago
a month ago
It works if i use another n8n that i created
But in the one that is all the workflow doesn´t (Is exaclty the same request)
There is any firewall, that i have to check or something?
a month ago
Unlikely it's firewall. It's probably something in the connection between n8n and chatwoot. Are you sure you're using the right credentials? The API key or webhook handle for the specific inbox are different.
Try both domains here on Postman using the official chatwoot Postman collection: https://www.postman.com/chatwoot/chatwoot-apis/collection/fu7fw8d/chatwoot-application-api-v1-0. You'll prolly find the issue in minutes.
a month ago
It´s the right api key, just doesn´t work anymore in this enviroment n8n, i just gonna create another n8n and delete the one i had
masterduque
It´s the right api key, just doesn´t work anymore in this enviroment n8n, i just gonna create another n8n and delete the one i had
a month ago
Yeah, if you don't have meaningful data there, just ditch the old one and use the new. Far smarter than trying to find the cause.
a month ago
In n8n you can enable verbose debugging by setting the env var “N8N_LOG_LEVEL=debug” , then you should open dev tools in workflow page and run the workflow, then check console for logs.
Use this to try to understand what is going wrong .
n8n has some weird bugs:
sometimes a NODE became broken even if it’s configuration is correct.Try to recreate the n8n node for the http request inside the workflow from scratch and check if works.
sometimes a WORKFLOW became broken even if it’s configuration is correct.Try to duplicate the n8n workflow and check if works. You can duplicate the workflow in two ways: use the duplicate workflow button , or copy all nodes and paste them in a blank workflow. TRY BOTH.
let me know if you make progress 