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 export a trunk configuration. Exporting a trunk is useful for backing up trunk settings, migrating configurations between systems, or auditing current telephony setups.

A practical example would be an administrator who wants to export the configuration of a specific trunk by its ID to save it externally or to replicate the setup on another 3CX instance.

Properties

Name Meaning
Id The unique identifier of the trunk entity to export. This is required and can be provided directly or via an expression (e.g., {{$json.Id}}).

Output

The node outputs JSON data representing the exported trunk configuration. This JSON contains all relevant details of the trunk as retrieved from the 3CX API. There is no indication that binary data is output by this operation.

Dependencies

  • Requires an API key credential for authenticating with the 3CX system.
  • Needs the base URL of the 3CX server configured in the credentials.
  • The node uses the 3CX REST API endpoint /xapi/v1 to perform operations.

Troubleshooting

  • Common issues:

    • Invalid or missing trunk ID will likely cause the export to fail.
    • Incorrect or expired API credentials will prevent successful communication with the 3CX server.
    • Network connectivity issues to the 3CX server can cause timeouts or connection errors.

  • Error messages:

    • Authentication errors typically indicate invalid API credentials; verify and update them.
    • "Entity not found" or similar errors suggest the provided trunk ID does not exist; confirm the ID is correct.
    • Timeout or network errors require checking server availability and network settings.

Links and References

Discussion