regarding n8n npm package

[suzukiahmed]

@devlikeapro/n8n-nodes-chatwoot

Installed above community node in self hosted n8n.
Problem is few are working few are not working.

What are not working?

1. Sending message through chatwoot (Error = Request failed with status code 422)
2. Fetching message history (Request failed with status code 404 for resource = conversation api , but the node is working if resource = contacts)

Why so? Is it npm package error or my config error?

[darekwojciechowski]

Both are HTTP responses from Chatwoot rejecting the request, not a broken node — the status codes tell you where to look:

422 (Unprocessable Entity) on "send message" means Chatwoot got the request but the payload is missing or has an invalid required field. The message endpoint needs a valid content and usually message_type. Turn on the node's verbose/response output and check the JSON body Chatwoot returns — it names the exact field. Common causes: empty content, wrong conversation_id, or message_type not set to outgoing.

404 (Not Found) on "fetch message history" means the URL path is wrong for that resource. Contacts working but conversations 404ing points to the account_id or conversation_id being wrong, so the node builds a path to a conversation that doesn't exist under that account. Chatwoot's API is scoped per account:
/api/v1/accounts/{account_id}/conversations/{conversation_id}/messages
Double-check the account_id in the credential/node matches the account the conversation actually belongs to (it's the number in your Chatwoot URL, /app/accounts/{id}/...).

So: for 422 read the returned error body and fill the missing field; for 404 fix the account_id / conversation_id. Both are config, not the npm package. To confirm, reproduce the same call with curl against your Chatwoot API using a manual access token — if curl returns the same 422/404, it's definitely the request data, not n8n.