3CX icon

3CX

Interact with 3CX telephony system
Join our community

Actions462

Overview

This node interacts with the 3CX telephony system to retrieve statistics about abandoned chats. Specifically, the "Get Abandoned Chats Statistics Data" operation fetches detailed data on abandoned chat sessions within a specified queue and time range. This is useful for contact center managers or administrators who want to analyze chat abandonment trends, optimize staffing, or improve customer service quality.

Practical examples include:

  • Monitoring how many chats were abandoned in a particular queue during peak hours.
  • Analyzing participant types involved in abandoned chats over a date range.
  • Filtering and sorting abandoned chat data to identify patterns or issues.

Properties

Name Meaning
Queue Dn Str The identifier string of the queue to query abandoned chat statistics for.
Start Dt The start date/time for the statistics data retrieval (format expected by the API).
End Dt The end date/time for the statistics data retrieval (format expected by the API).
Participant Type Numeric value indicating the type of participant to filter the abandoned chats by.
Options Additional query options to refine the results:
- Top Show only the first n items (pagination limit).
- Skip Skip the first n items (pagination offset).
- Search Search items by search phrases; supports quoted phrases for exact matches.
- Filter Filter items by property values using OData-like syntax (e.g., State eq 'Connected').
- Count Boolean flag to include the count of items in the response.
- Select Select specific properties to be returned (comma-separated list).
- Orderby Order items by property values (e.g., Name desc, CreatedAt asc).
- Expand Expand related entities to include additional linked data.

Output

The node outputs JSON data containing the abandoned chat statistics matching the input criteria. The structure typically includes an array of records representing individual abandoned chat entries or aggregated statistics, depending on the API response.

If binary data were supported, it would represent downloadable reports or files, but this node focuses on JSON data output.

Dependencies

  • Requires an API key credential for authenticating with the 3CX telephony system.
  • Needs the base URL of the 3CX server configured in credentials.
  • Relies on the 3CX REST API endpoint /xapi/v1 for fetching abandoned chat statistics.
  • No other external dependencies are indicated.

Troubleshooting

  • Common Issues:

    • Incorrect or missing queue identifier (queueDnStr) may result in empty or error responses.
    • Date formats for startDt and endDt must match the API expectations; otherwise, the request may fail.
    • Insufficient permissions or invalid API credentials will cause authentication errors.
    • Using unsupported or malformed filter/search queries can lead to API errors.

  • Error Messages:

    • Authentication failures: Verify API key and server URL in credentials.
    • Validation errors on parameters: Check required fields and their formats.
    • Network or connectivity issues: Ensure the 3CX server is reachable from n8n.

Links and References

Discussion