ChatWoot

Overview

This node interacts with the ChatWoot API to assign a conversation to either a specific user or a team within an account. It is useful in customer support workflows where conversations need to be routed to the appropriate agent or team for handling. For example, when a new customer message arrives, this node can automatically assign the conversation to a designated support agent or escalate it to a specialized team.

Properties

Output

The node outputs JSON data representing the response from the ChatWoot API after attempting to assign the conversation. This typically includes details about the updated conversation assignment status. The output does not include binary data.

Dependencies

• Requires an API key credential for authenticating with the ChatWoot API.
• The base URL of the ChatWoot instance must be configured in the credentials.
• The node depends on the ChatWoot REST API being accessible and properly configured.

Troubleshooting

• Common issues:
  • Invalid or missing API credentials will cause authentication errors.
  • Providing both assignee_id and team_id may lead to unexpected behavior; the node prioritizes assignee_id.
  • Using incorrect numeric IDs (account, conversation, assignee, or team) will result in "not found" or similar API errors.
• Error messages:
  • Authentication failures: Verify that the API key and base URL are correct.
  • Resource not found: Confirm that the account, conversation, user, or team IDs exist in ChatWoot.
  • Validation errors: Ensure required fields (account_id, conversation_id) are provided and valid numbers.

Links and References

• ChatWoot API Documentation
• ChatWoot Official Website