3CX icon

3CX

Interact with 3CX telephony system
Join our community

Actions462

Overview

The node interacts with the 3CX telephony system, specifically providing functionality to provision device information. This operation is useful in scenarios where you need to register or update devices within the 3CX system programmatically. For example, it can be used to automate the setup of new phones or reconfigure existing ones by sending provisioning commands directly from an n8n workflow.

Properties

Name Meaning
Id The unique identifier of the device entity to provision. Can be set dynamically via expressions.
Reprovision A boolean flag indicating whether to reprovision the device (true) or not (false).
User Id The user ID associated with the device, used for provisioning purposes.

Output

The node outputs JSON data representing the result of the provisioning request to the 3CX system. This typically includes status information about the provisioning process and any relevant response details from the API. There is no indication that the node outputs binary data.

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 sends HTTP requests to the 3CX API endpoint /xapi/v1.

Troubleshooting

  • Common issues:

    • Incorrect or missing API credentials will cause authentication failures.
    • Providing an invalid or non-existent device Id may result in errors or no action.
    • Network connectivity problems to the 3CX server will prevent successful provisioning.

  • Error messages:

    • Authentication errors usually indicate invalid or expired API tokens; verify and update credentials.
    • "Device not found" or similar errors suggest the provided Id does not exist; check the Id value.
    • Timeout or connection errors imply network issues; ensure the server URL is reachable.

Links and References

Discussion