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 detailed information about a specific conversation within a given account. It is useful when you need to fetch all available data related to a particular conversation, such as messages exchanged, participants, status, and metadata. Practical applications include customer support workflows where agents or automation processes require full context of a conversation to provide assistance or perform analytics.
Properties
| Name | Meaning |
|---|---|
| Account Id | The numeric ID of the ChatWoot account from which to fetch the conversation details. |
| Conversation Id | The numeric ID of the specific conversation whose details are to be retrieved. |
Output
The node outputs JSON data representing the full details of the requested conversation. This typically includes conversation metadata, message history, participant information, timestamps, and status fields. The output structure directly reflects the response schema of the ChatWoot API endpoint for fetching conversation details.
No binary data output is produced 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 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 return an error. Verify that the numeric IDs are correct and correspond to existing resources.
- Authentication Errors: Ensure the API key credential is correctly set up and has sufficient permissions to access conversation data.
- Network Issues: Connectivity problems or incorrect base URL configuration can cause request failures. Confirm the ChatWoot instance URL is reachable.
- 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 - Official API docs for reference on conversation endpoints.
- n8n Documentation - For general guidance on using API nodes and managing credentials.