3CX icon

3CX

Interact with 3CX telephony system
Join our community

Actions462

Overview

This node interacts with the 3CX telephony system, specifically providing an operation to list time zones defined in the system. It is useful for workflows that need to retrieve and work with time zone data from 3CX, such as scheduling calls, setting up time-based rules, or displaying available time zones for user selection.

A practical example would be a workflow that fetches all available time zones to populate a dropdown menu in a user interface or to validate user input against supported time zones.

Properties

Name Meaning
Options A collection of optional query parameters to customize the listing of time zones:
$top Show only the first n items (limit the number of results returned).
$skip Skip the first n items (useful for pagination).
$search Search items by search phrases; supports phrase searching with quotes if needed.
$filter Filter items by property values using OData filter syntax (e.g., State eq 'Connected').
$count Include count of items in the response (boolean).
$orderby Order items by property values (e.g., Name desc, CreatedAt asc).
$select Select specific properties to be returned (e.g., Id,Name).
$expand Expand related entities (e.g., RelatedEntity1,RelatedEntity2).

Output

The node outputs JSON data representing the list of time zones retrieved from the 3CX API. The structure typically includes an array of time zone objects, each containing properties such as ID, name, and possibly other metadata depending on the selected fields.

If binary data were involved, it would represent file contents or media streams, but this node deals solely with JSON data.

Dependencies

  • Requires an active connection to a 3CX telephony system.
  • Needs an API authentication token credential configured in n8n to authorize requests.
  • The base URL for the 3CX API must be provided in the credentials configuration.
  • The node sends HTTP requests to the 3CX API endpoint /xapi/v1.

Troubleshooting

  • Authentication errors: Ensure the API key or OAuth2 token is valid and has sufficient permissions.
  • Invalid query parameters: Using incorrect syntax in options like $filter or $orderby may cause API errors. Verify the OData syntax and property names.
  • Empty results: If no time zones are returned, check the $search, $filter, and pagination parameters to ensure they match existing data.
  • Connection issues: Confirm the server URL is correct and reachable from the n8n instance.

Links and References

Discussion