Actions113
- 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
- Contacts API Actions
- Inbox API Actions
- Conversations API Actions
- Messages API Actions
- CSAT Survey Page Actions
- Account Agent Bots Actions
- Agents Actions
- Canned Responses Actions
- Custom Attributes Actions
- Canned Response 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 before responding or to analyze communication patterns.
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 you want to retrieve. |
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 aligns with the ChatWoot API response for contact conversations.
No binary data output is indicated.
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 failures.
- Incorrect Account Id or Contact Id values may result in empty responses or errors.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Authentication errors usually indicate invalid API keys or misconfigured credentials.
- "Not Found" errors suggest that the specified contact or account does not exist.
- Rate limiting errors may occur if too many requests are sent in a short period; retry after some time.