Error 404 even with APP configured

[HermesMacedo]

Full message

Request failed with status code 404
Error data

{ "status": 404, "error": "Not Found"

I'm using the Platform App token. Is this correct? Or is it the admin user token?

Congratulations on the node. Is there any kind of $$ support plan for it?

[devlikepro]

It requires 2 tokens - super admin and inbox
See details in #4 (comment)

Is there any kind of $$ support plan for it?

What support would you like to get?
WAHA PRO tier includes consultations in Discord https://waha.devlike.pro/pricing/

[rafa-guzzo]

Hi, I am having the same issue as OP. I am using the profile token, I can get it to work through http, but it simply aways return 404 with your nodes. I noticed on your reply you link to a different post where the user was missing the Inbox identifier, it is not necessary for list conversations, I am simply using the profile token, and i can get the API to work through http.

Here is the full error

{
"errorMessage": "The resource you are requesting could not be found",
"errorDescription": "Request failed with status code 404",
"errorDetails": {
"rawErrorMessage": [
"Request failed with status code 404"
],
"httpCode": "404",
"errorData": {
"error": "Resource could not be found"
}
},
"n8nDetails": {
"nodeName": "ChatWoot",
"nodeType": "@devlikeapro/n8n-nodes-chatwoot.chatWoot",
"nodeVersion": 1,
"resource": "Conversations",
"operation": "Conversation List",
"itemIndex": 0,
"runIndex": 0,
"time": "17/03/2025, 14:27:02",
"n8nVersion": "1.83.2 (Self Hosted)",
"binaryDataMode": "default",
"stackTrace": [
"NodeApiError: The resource you are requesting could not be found",
" at ExecuteSingleContext.httpRequestWithAuthentication (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/node-execution-context/utils/request-helper-functions.js:946:15)",
" at processTicksAndRejections (node:internal/process/task_queues:95:5)",
" at ExecuteSingleContext.httpRequestWithAuthentication (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/node-execution-context/utils/request-helper-functions.js:1143:20)",
" at RoutingNode.rawRoutingRequest (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/routing-node.js:319:29)",
" at RoutingNode.makeRequest (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/routing-node.js:406:28)",
" at async Promise.allSettled (index 0)",
" at RoutingNode.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/routing-node.js:139:35)",
" at ExecuteContext.versionedNodeType.execute (/usr/local/lib/node_modules/n8n/dist/node-types.js:52:30)",
" at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:681:27)",
" at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:913:51"
]
}
}

[devlikepro]

Hi!
Looks like it's because of https://community.n8n.io/t/null-and-undefined-in-string-fields/31060/3
So when you set any values in other field, like inbox_id, team_id it tries to convert it to the "null/undefined" or other values.

When you set the values - it does return the result

[devlikepro]

For the null/undefined issue probably we can do fix in in some ways, but it needs to be done in the underlying lib chatwoot node uses
devlikeapro/n8n-openapi-node#8

We also need to add more logs in the response, it's super hard to understand right now what is going on
devlikeapro/n8n-openapi-node#7