3CX icon

3CX

Interact with 3CX telephony system
Join our community

Actions462

Overview

This node integrates with the 3CX telephony system, specifically allowing users to delete a phone template by its unique identifier. It is useful in scenarios where phone templates are no longer needed or must be removed to maintain an organized telephony configuration. For example, if a company updates its call routing policies and certain phone templates become obsolete, this node can automate their deletion.

Properties

Name Meaning
Id The unique identifier of the phone template to delete. Can be set using expressions like {{$json.Id}}.
If Match Optional ETag header value for concurrency control. Ensures the template is deleted only if it matches the specified version.

Output

The node outputs JSON data representing the result of the delete operation. Typically, this will include confirmation of successful deletion or error details if the operation failed. There is no binary output associated with this node.

Dependencies

  • Requires an API key credential for authenticating with the 3CX telephony 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:

    • Providing an incorrect or missing template Id will cause the deletion to fail.
    • Using an outdated or incorrect ETag value in the "If Match" property may result in a concurrency error.
    • Network connectivity problems or incorrect server URL configuration can prevent communication with the 3CX API.

  • Error messages:

    • 404 Not Found: The specified phone template Id does not exist.
    • 412 Precondition Failed: The ETag provided in "If Match" does not match the current version of the resource.
    • 401 Unauthorized: Authentication failed due to invalid or missing API credentials.

To resolve these errors, verify the template Id, update the ETag if used, and ensure valid authentication credentials and server URL are configured.

Links and References

Discussion