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
- Webhooks Actions
- Teams Actions
- Custom Filters 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 engagement platform. For example, a user might use this node to display conversation history for a contact in a CRM workflow or to analyze past interactions for customer service purposes.
Properties
| Name | Meaning |
|---|---|
| Account Id | The numeric ID of the account to which the contact belongs. |
| Id | The unique numeric ID of the contact whose conversations are being fetched. |
Output
The node outputs JSON data representing the contact's conversations retrieved from the ChatWoot API. This typically includes details such as conversation IDs, messages, timestamps, participants, and status. The output structure follows the API response format for contact conversations. There is no indication that binary data is returned by this operation.
Dependencies
- Requires an API key credential for authenticating with the ChatWoot API.
- The base URL for the ChatWoot instance must be configured in the node credentials.
- The node depends on the
@devlikeapro/n8n-openapi-nodepackage for OpenAPI integration.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication errors.
- Providing incorrect account or contact IDs may result in "not found" errors or empty responses.
- Network connectivity problems can lead to request timeouts or failures.
Error messages:
- Authentication errors usually indicate invalid API keys or misconfigured credentials.
- 404 errors suggest that the specified account or contact does not exist.
- Rate limiting errors may occur if too many requests are sent in a short period; retry after some time.