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 list all messages within a specific conversation of an account. It is useful for retrieving message histories, monitoring conversations, or integrating ChatWoot messaging data into workflows. For example, you might use this node to fetch all messages from a customer support conversation to analyze chat interactions or trigger follow-up actions based on message content.
Properties
| Name | Meaning |
|---|---|
| Account Id | The numeric ID of the ChatWoot account. |
| Conversation Id | The numeric ID of the conversation to query. |
Output
The node outputs JSON data representing the list of messages retrieved from the specified conversation. Each item in the output corresponds to a message object as returned by the ChatWoot API, typically including details such as message content, sender information, timestamps, and message status. The node does not output binary data.
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 are incorrect or do not exist, the API will likely return an error or empty results. Verify that the IDs correspond to existing resources in your ChatWoot instance.
- Authentication Errors: Ensure the API key credential is correctly set up and has sufficient permissions to access messages.
- Network Issues: Connectivity problems to the ChatWoot server can cause request failures. Check network settings and endpoint availability.
- API Rate Limits: Excessive requests may lead to rate limiting; consider adding delays or handling retries gracefully.
Links and References
- ChatWoot API Documentation (for detailed API endpoints and message object structure)
- n8n Documentation (for general guidance on using API nodes and credentials)