Actions113
- 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
- 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
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 communication patterns.
Properties
| Name | Meaning |
|---|---|
| Account Id | The numeric ID of the account to query. |
| Id | The ID of the contact whose conversations are being 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, 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
- Invalid Account Id or Contact Id: If the provided IDs do not exist or are incorrect, the API will likely return an error or empty results. Verify the IDs before running the node.
- Authentication Errors: Ensure the API key credential is valid and has sufficient permissions to access contact conversations.
- Network Issues: Connectivity problems with the ChatWoot server can cause request failures. Check network settings and endpoint availability.
- API Rate Limits: Excessive requests may lead to rate limiting; handle such errors by implementing retries or backoff strategies.
Links and References
- ChatWoot API Documentation (for detailed API endpoints and data structures)
- n8n OpenAPI Node Integration