3CX icon

3CX

Interact with 3CX telephony system
Join our community

Actions462

Overview

This node interacts with the 3CX telephony system to retrieve historical call log data. Specifically, the "Get Old Call Log Data" operation under the "Report Call Log Data" resource allows users to query detailed call records within a specified time period and apply various filters on source, destination, call types, and call times.

Typical use cases include:

  • Generating reports on past call activity for analysis or auditing.
  • Filtering call logs by specific phone numbers or extensions.
  • Extracting call data for integration with CRM or analytics platforms.
  • Monitoring call patterns over custom date ranges.

For example, a user might fetch all calls made from a particular extension between two dates, excluding certain call types, to analyze call volume trends.

Properties

Name Meaning
Period From Start date/time of the period to retrieve call logs (format as required by the API).
Period To End date/time of the period to retrieve call logs.
Source Type Numeric code representing the type of source (e.g., extension, external number).
Source Filter Filter string to specify which sources to include (e.g., specific extensions or numbers).
Destination Type Numeric code representing the type of destination (e.g., extension, external number).
Destination Filter Filter string to specify which destinations to include.
Calls Type Numeric code indicating the type of calls to include (e.g., incoming, outgoing, missed).
Call Time Filter Type Numeric code defining how to filter calls based on call time (e.g., start time, answer time).
Call Time Filter From Start time for the call time filter.
Call Time Filter To End time for the call time filter.
Hide Pcalls Boolean flag to exclude certain call types labeled as "Pcalls" (likely internal or special calls).
Options Collection of optional OData-like 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 restrict results by property values (e.g., State eq 'Connected').
- Count Boolean to include the count of total items matching the query.
- Select Comma-separated list of properties to return for each item.
- Orderby Property names and directions to order the results (e.g., Name desc).
- Expand Related entities to expand/include in the response.

Output

The node outputs JSON data containing the retrieved call log records matching the specified criteria. Each record typically includes details such as call timestamps, source and destination identifiers, call duration, call status, and other metadata provided by the 3CX API.

If binary data is present (not indicated here), it would represent associated media like call recordings, but this operation appears focused on JSON call log data only.

Dependencies

  • Requires an active connection to a 3CX telephony system via its API.
  • 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 credentials.
  • The node uses standard HTTP headers accepting JSON responses.

Troubleshooting

  • Authentication errors: Ensure the API key or OAuth2 token is valid and has sufficient permissions.
  • Invalid date formats: The "Period From", "Period To", and call time filters must be formatted according to the 3CX API requirements; incorrect formats may cause request failures.
  • Empty results: Check that filters are not overly restrictive; verify that the date range actually contains call data.
  • API rate limits or connectivity issues: Network problems or API throttling can cause errors; retry after some time or check network settings.
  • Incorrect numeric codes: Using invalid values for source/destination/call types or filter types may lead to unexpected results or errors.

Links and References

Discussion