ChatWoot icon

ChatWoot

Interact with ChatWoot API

Actions113

Reports → List All Conversation Statistics Summary

AI-generated

Overview

This node operation "List All Conversation Statistics Summary" under the "Reports" resource fetches summarized conversation statistics from a ChatWoot account. It is useful for generating aggregated reports on conversations filtered by different entities such as accounts, agents, inboxes, labels, or teams over a specified time range.

Typical use cases include:

  • Monitoring overall conversation metrics for an account.
  • Analyzing agent performance by retrieving conversation stats per agent.
  • Evaluating inbox activity or label-specific conversation summaries.
  • Tracking team-based conversation statistics to assess workload or efficiency.

For example, a customer support manager could use this node to pull monthly conversation summaries for a specific team to evaluate their handling capacity and response trends.

Properties

Name Meaning
Account Id The numeric ID of the ChatWoot account for which the report is generated (required).
Type The type of report to generate. Options: Account, Agent, Inbox, Label, Team (required).
Id The identifier of the specific object when the type is agent, inbox, or label (optional).
Since The start timestamp (ISO string) from which to begin the report data (optional).
Until The end timestamp (ISO string) at which to stop the report data (optional).

Output

The node outputs JSON data containing the summarized conversation statistics according to the selected type and filters. The structure typically includes aggregated metrics such as counts of conversations, messages, response times, and other relevant summary fields depending on the report type.

No binary data output is indicated for this operation.

Dependencies

  • Requires connection to a ChatWoot instance via its API.
  • Needs an API authentication token configured in the node credentials.
  • The base URL of the ChatWoot API must be set in the credentials.
  • The node uses query parameters to send filtering options like type, id, since, and until.

Troubleshooting

  • Missing or invalid Account Id: Ensure the Account Id is provided and is a valid number; otherwise, the API call will fail.
  • Invalid timestamps: The since and until properties should be valid ISO 8601 date strings; incorrect formats may cause errors or empty results.
  • Incorrect Type or Id mismatch: If the type is set to agent, inbox, or label, ensure the corresponding id is provided; missing or wrong IDs can lead to no data or errors.
  • Authentication errors: Verify that the API key/token and base URL are correctly configured in the credentials.
  • API rate limits or connectivity issues: Network problems or hitting API limits may cause request failures; check network and API usage policies.

Links and References

Discussion