3CX icon

3CX

Interact with 3CX telephony system
Join our community

Actions462

Overview

This node interacts with the 3CX telephony system, specifically providing functionality to retrieve information about FXS (Foreign Exchange Station) devices by their MAC address. It is useful in scenarios where you need to query detailed configuration or status of specific telephony hardware connected to the 3CX system.

A practical example would be an automation workflow that, given a MAC address from an incoming data source, fetches the corresponding FXS device details for monitoring, reporting, or further processing.

Properties

Name Meaning
Mac Address The MAC address key of the FXS device to retrieve. Supports expressions, e.g., {{$json.MacAddress}}. This is a required string input.
Options Additional query options to customize the returned data:
- Select Comma-separated list of properties to return (e.g., "Id,Name").
- Expand Comma-separated list of related entities to expand and include in the response.

Output

The node outputs JSON data representing the FXS device details retrieved from the 3CX system. The structure depends on the selected properties and expanded related entities but generally includes identifiers, names, and other configuration or status fields of the FXS device.

No binary data output is indicated.

Dependencies

  • Requires connection to a 3CX telephony system API.
  • Needs an API authentication token configured via credentials in n8n (an OAuth2 API credential).
  • The base URL for the 3CX server must be provided in the credentials configuration.

Troubleshooting

  • Common issues:
    • Invalid or missing MAC address input will cause the request to fail.
    • Incorrect or expired API authentication token will result in authorization errors.
    • Network connectivity problems to the 3CX server can cause timeouts or connection failures.
  • Error messages:
    • Authorization errors typically indicate invalid credentials; reconfigure the API token.
    • "Not Found" errors may mean the MAC address does not exist in the system.
    • Malformed query parameters in options may lead to bad request errors; ensure correct syntax.

Links and References

Discussion