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 detailed information about a specific conversation within a given account. It is useful for scenarios where you need to fetch comprehensive data about customer interactions, support tickets, or chat sessions managed in ChatWoot. For example, a support team could use this node to automatically pull conversation details for analysis or to trigger follow-up actions based on conversation content.
Properties
| Name | Meaning |
|---|---|
| Account Id | The numeric ID of the ChatWoot account from which to retrieve the conversation details. |
| Conversation Id | The numeric ID of the specific conversation whose details are to be fetched. |
Output
The node outputs JSON data containing the full details of the specified conversation. This typically includes metadata such as participants, messages, timestamps, status, and any other relevant conversation attributes provided by the ChatWoot API. There is no binary output.
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 ChatWoot REST API being accessible and the provided account and conversation IDs being valid.
Troubleshooting
- Invalid Account or Conversation ID: If the IDs do not exist or are incorrect, the API will likely return an error indicating the resource was not found. Verify the IDs before running the node.
- Authentication Errors: Ensure that the API key credential is correctly set up and has sufficient permissions to access conversation data.
- Network Issues: Connectivity problems to the ChatWoot server can cause timeouts or 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)