ChatWoot icon

ChatWoot

Interact with ChatWoot API

Actions113

Overview

This node interacts with the ChatWoot API to list conversations within a specified account. It is useful for retrieving and filtering conversations based on various criteria such as assignee type, status, search terms, inbox, team, labels, and pagination. Typical use cases include monitoring customer support conversations, generating reports on conversation statuses, or integrating conversation data into other workflows.

For example, a user might want to fetch all open conversations assigned to their team in a particular inbox to display them in a dashboard or trigger follow-up actions.

Properties

Name Meaning
Account Id The numeric ID of the account whose conversations are to be listed (required).
Assignee Type Filter conversations by assignee type. Options: Me, Unassigned, All, Assigned.
Status Filter conversations by their status. Options: Open, Resolved, Pending, Snoozed.
Q Search term to filter conversations containing messages matching this string.
Inbox Id Numeric ID of the inbox to filter conversations by.
Team Id Numeric ID of the team to filter conversations by.
Labels JSON array of labels to filter conversations by.
Page Page number for paginating through conversations. Defaults to 1.

Output

The node outputs a JSON array of conversation objects retrieved from the ChatWoot API according to the applied filters. Each conversation object typically contains details such as conversation ID, status, assignee information, messages, timestamps, labels, and related metadata.

If binary data were involved (e.g., attachments), it would be included accordingly, but this operation focuses on listing conversation metadata only.

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.
  • No additional external dependencies beyond the ChatWoot API.

Troubleshooting

  • Invalid Account Id: Ensure the provided account ID exists and the API key has access rights.
  • Authentication Errors: Verify that the API key credential is correctly set up and has necessary permissions.
  • Empty Results: Check filter parameters; overly restrictive filters may return no conversations.
  • Pagination Issues: If many conversations exist, ensure the Page parameter is used correctly to navigate results.
  • Malformed Labels JSON: The Labels property expects valid JSON; invalid JSON will cause errors.

Links and References

Discussion