Voicenter icon

Voicenter

Consume Voicenter API (v.0.1.7)

Actions10

Overview

The node integrates with the Voicenter API to retrieve detailed call record information from the call log. It is designed to fetch specific call records based on various search criteria such as date ranges, phone numbers, extensions, and identity criteria. This node is useful in scenarios where users need to analyze or audit call activities, generate reports, or integrate call data into other workflows.

For example, a customer support team might use this node to pull call details for a given period to evaluate call durations and identify peak call times. Similarly, sales teams could extract call records filtered by specific representatives or departments to monitor performance.

Properties

Name Meaning
Search Collection of filters to narrow down call records:
- Fromdate Start date/time (ISO 8601) to filter calls from.
- Todate End date/time (ISO 8601) to filter calls up to.
- Phones List of phone numbers (with country codes) to include in the search.
- Extensions List of Voicenter SIP trunk extensions to filter calls by.
- IdentityCriteria Criteria to identify calls by Account, Hierarchical structure, Department, or User.
Fields Specifies which fields to return in the response. Default includes Date, Type, DID, CallerNumber, etc.
ParamsAsJson Boolean flag to enable merging additional JSON parameters into the request using lodash's merge function.
JsonBody Raw JSON input to append or override parameters when ParamsAsJson is enabled.

Output

The output contains a JSON object representing the call record details matching the specified search criteria. The fields returned correspond to those selected in the "Fields" property, such as:

  • Date: Timestamp of the call.
  • Type: Call type (e.g., inbound, outbound).
  • DID: Direct Inward Dialing number.
  • CallerNumber: Phone number of the caller.
  • CallerExtension: Extension used by the caller.
  • TargetNumber: Number called.
  • Duration: Length of the call.
  • RecordURL: URL to the call recording if available.
  • RepresentativeName: Name of the representative involved in the call.

If binary data (such as call recordings) is included, it will be represented as URLs or references rather than raw binary content.

Dependencies

  • Requires an active Voicenter API credential (API key or token) configured in n8n.
  • Uses the Voicenter API client internally to perform authenticated requests.
  • Optional usage of lodash's merge function to combine JSON parameters if ParamsAsJson is enabled.

Troubleshooting

  • Authentication errors: Ensure that the API credentials are correctly set up and valid.
  • Empty results: Verify that the search criteria (dates, phones, extensions) are correct and that there are matching call records.
  • Invalid date formats: Dates must be in ISO 8601 format; otherwise, the API may reject the request.
  • Malformed JSON: If using the JsonBody property, ensure the JSON syntax is valid to avoid parsing errors.
  • Field selection issues: Requesting unsupported or misspelled fields may result in incomplete data or errors.

Links and References

Discussion