ChatWoot icon

ChatWoot

Interact with ChatWoot API

Actions113

Overview

This node interacts with the ChatWoot API to retrieve canned responses associated with a specific account. The "Get Account Canned Response" operation fetches predefined message templates (canned responses) that can be used for quick replies in customer support scenarios. This is useful for support agents or automated workflows that need to access and utilize standardized responses efficiently.

Practical examples include:

  • Automatically fetching canned responses to suggest replies in a chatbot.
  • Integrating with helpdesk systems to display available response templates.
  • Using canned responses in automation workflows to maintain consistent communication.

Properties

Name Meaning
Account Id The numeric ID of the account to fetch canned responses from

Output

The node outputs JSON data containing the list of canned responses retrieved from the specified account. Each item typically includes details such as the response content, identifier, and metadata related to the canned response.

If the API supports it, the output may also include additional fields describing each canned response's usage or categorization.

No binary data output is indicated by the source code.

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 @devlikeapro/n8n-openapi-node package for OpenAPI integration.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Providing an incorrect or non-existent Account Id will result in empty or error responses.
    • Network connectivity problems to the ChatWoot server can cause request timeouts or failures.
  • Error messages:

    • Authentication errors typically indicate invalid API keys or misconfigured credentials.
    • "Not Found" errors may mean the specified account does not exist or the user lacks permission.
    • JSON parsing errors could occur if the API response format changes unexpectedly.

To resolve these:

  • Verify API credentials and permissions.
  • Confirm the Account Id is correct and accessible.
  • Check network connectivity and endpoint URLs.

Links and References

Discussion