3CX icon

3CX

Interact with 3CX telephony system
Join our community

Actions462

Overview

This node interacts with the 3CX telephony system to retrieve detailed reports on queue answered calls categorized by wait time. Specifically, the "Get Queue Answered Calls By Wait Time Data" operation fetches data about calls that were answered in a particular queue within a specified time range and grouped by answer intervals.

Common scenarios for this node include:

  • Monitoring call center performance by analyzing how long callers wait before their calls are answered.
  • Generating reports to optimize staffing and reduce wait times.
  • Tracking trends in call answering efficiency over specific periods.

For example, a user might configure the node to get all answered calls in queue "SalesQueue" between January 1st and January 31st, grouped by 5-minute intervals, to understand peak wait times and improve customer service.

Properties

Name Meaning
Queue Dn Str The identifier string of the queue to query (e.g., queue phone number or name).
Start Dt The start date/time for the report data range (format as required by the API).
End Dt The end date/time for the report data range.
Answer Interval The interval grouping for answered calls by wait time (e.g., "5m" for 5 minutes).
Options Additional optional query parameters:
- Top Limit the number of returned items to the first n entries.
- Skip Skip the first n items in the result set.
- Search Search phrase(s) to filter items by text matching.
- Filter Filter expression to narrow down results by property values (e.g., State eq 'Connected').
- Count Boolean flag to include the count of total items in the response.
- Select Comma-separated list of properties to return (e.g., Id,Name).
- Orderby Property names and directions to order results (e.g., Name desc).
- Expand Related entities to expand in the response.

Output

The node outputs JSON data representing the queue answered calls grouped by wait time intervals. Each item typically includes details such as the queue identifier, the time interval, and statistics about the answered calls (counts, durations, etc.).

If binary data is supported (not indicated here), it would represent related media or files, but this node primarily returns structured JSON report data.

Dependencies

  • Requires an active connection to a 3CX telephony system via an API endpoint.
  • Needs an API authentication token or OAuth2 credential configured in n8n to authorize requests.
  • The base URL for the 3CX API must be correctly set in the node credentials.
  • The node uses standard HTTP headers accepting JSON responses.

Troubleshooting

  • Missing or invalid credentials: Ensure the API key or OAuth2 token is valid and has sufficient permissions.
  • Incorrect date formats: The Start Dt and End Dt must be formatted according to the API's expected datetime format.
  • Invalid queue identifier: Verify that the Queue Dn Str matches an existing queue in the 3CX system.
  • Empty or no data returned: Check if the date range and filters actually match any answered calls; try broadening the criteria.
  • API rate limits or connectivity issues: Confirm network access to the 3CX server and check for any throttling or downtime.

Links and References

Discussion