Chatwoot icon

Chatwoot

Interact with Chatwoot API

Overview

This node interacts with the Chatwoot API to manage messages within conversations. Specifically, the Message - Get Many operation retrieves multiple messages from a specified conversation by its numeric ID. This is useful for scenarios where you want to fetch the entire message history or a batch of messages from a conversation for analysis, reporting, or further processing.

Practical examples:

  • Fetching all messages in a customer support conversation to analyze communication patterns.
  • Retrieving recent chat messages to display in a custom dashboard.
  • Exporting conversation messages for archival or compliance purposes.

Properties

Name Meaning
Conversation ID The numeric ID of the conversation from which to retrieve messages (required).
Continue on Fail Whether the node should continue processing subsequent items if this operation fails.
Debug Logging Whether to output detailed request and response information to the console for debugging.

Output

The node outputs an array of JSON objects, each representing a message retrieved from the specified conversation. Each item corresponds to one message's data as returned by the Chatwoot API under the conversation's messages endpoint.

The structure of each JSON object includes all standard message fields provided by Chatwoot, such as message content, sender info, timestamps, and any metadata associated with the message.

This node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating with the Chatwoot API.
  • Needs the account ID and base URL configured in the credentials.
  • The node makes HTTP GET requests to the Chatwoot API endpoint /api/v1/accounts/{accountId}/conversations/{conversationId}/messages.

Troubleshooting

  • Invalid Conversation ID: If the conversation ID does not exist or is incorrect, the API will return an error. Verify the conversation ID is correct.
  • Authentication Errors: Ensure the API key credential is valid and has access to the specified account.
  • API Rate Limits: Excessive requests may be throttled by Chatwoot; consider adding delays or handling rate limit errors gracefully.
  • JSON Parsing Errors: Not applicable here since the node only performs GET requests and maps the payload directly.
  • Network Issues: Check connectivity to the Chatwoot instance URL.

If "Debug Logging" is enabled, detailed logs will appear in the console to help diagnose issues related to URL construction, request headers, and responses.

Links and References

Discussion