Actions113
- Accounts Actions
- Account Users Actions
- Agent Bots Actions
- Users Actions
- Inbox API Actions
- Contacts API Actions
- Conversations API Actions
- Messages API Actions
- CSAT Survey Page Actions
- Account Agent Bots Actions
- Agents Actions
- Canned Responses Actions
- Canned Response Actions
- Custom Attributes Actions
- Contacts Actions
- Contact Actions
- Automation Rule Actions
- Help Center Actions
- Conversations Actions
- Conversation Assignment Actions
- Conversation Labels Actions
- Inboxes Actions
- Messages Actions
- Integrations Actions
- Teams Actions
- Custom Filters Actions
- Webhooks Actions
- Reports Actions
Overview
This node interacts with the ChatWoot API to retrieve conversations related to a specific contact within an account. It is useful for scenarios where you want to fetch all chat conversations or message threads associated with a particular contact in your customer support or CRM system powered by ChatWoot. For example, a user might use this node to display conversation history of a contact before responding or to analyze communication patterns.
Properties
| Name | Meaning |
|---|---|
| Account Id | The numeric ID of the ChatWoot account. |
| Id | The numeric ID of the contact whose conversations are to be retrieved. |
Output
The node outputs JSON data representing the contact's conversations fetched from the ChatWoot API. This typically includes details such as conversation IDs, messages, timestamps, status, and other metadata related to each conversation thread. There is no indication that binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the ChatWoot API.
- The base URL for the ChatWoot instance must be configured in the credentials.
- Depends on the
@devlikeapro/n8n-openapi-nodepackage for building request properties and handling OpenAPI specifications.
Troubleshooting
- Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrect Account Id or Contact Id values may result in empty responses or errors indicating resource not found.
- Network connectivity problems can prevent successful API calls.
- Error messages:
- Authentication errors usually indicate invalid API keys or misconfigured credentials.
- "Not Found" errors suggest the specified account or contact does not exist.
- Timeout or network errors imply connectivity issues; verify network access and endpoint availability.