ChatWoot icon

ChatWoot

Interact with ChatWoot API

Actions113

Overview

This node integrates with the ChatWoot API to add labels to a specific conversation within an account. It is useful for categorizing or tagging conversations automatically based on certain criteria, which helps in organizing and filtering conversations in customer support workflows.

Practical examples include:

  • Automatically tagging conversations that mention specific keywords.
  • Adding priority labels to conversations from VIP customers.
  • Categorizing conversations by issue type for reporting purposes.

Properties

Name Meaning
Account Id The numeric ID of the ChatWoot account where the conversation exists.
Conversation Id The numeric ID of the conversation to which labels will be added.
Labels An array of label strings (comma-separated) to add to the conversation.

Output

The node outputs JSON data representing the response from the ChatWoot API after adding the labels. This typically includes details about the updated conversation or confirmation of the label addition. 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 credentials.
  • The node uses the ChatWoot REST API endpoint for managing conversation labels.

Troubleshooting

  • Invalid Account or Conversation ID: Ensure the provided numeric IDs exist and belong to the authenticated account.
  • Malformed Labels JSON: The labels property expects a valid JSON array of strings. Invalid JSON or incorrect formatting will cause errors.
  • Authentication Errors: Verify that the API key credential is correctly set up and has sufficient permissions.
  • API Endpoint Issues: Confirm the base URL is correct and the ChatWoot server is reachable.

Common error messages may include HTTP 401 Unauthorized (authentication failure), 404 Not Found (invalid account or conversation), or 400 Bad Request (invalid input data). Resolving these involves checking credentials, IDs, and input formats.

Links and References

Discussion