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 queue within 3CX. It is useful in scenarios where you need to programmatically manage call queues, such as removing obsolete or unused queues from your telephony setup. For example, if a department is closed or merged, you can automate the cleanup of its associated call queue.

Properties

Name Meaning
Id The unique identifier of the queue to delete. You can provide this directly or via an expression like {{$json.Id}}.
If Match An optional ETag value used for concurrency control. This ensures the queue 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 confirm whether the queue was successfully deleted or provide error details if the deletion failed. There is no indication that binary data is output by this node.

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:

    • Providing an incorrect or non-existent queue ID will result in an error indicating the queue could not be found.
    • Using an outdated or incorrect ETag in the "If Match" property may cause the delete operation to fail due to concurrency conflicts.
    • Network connectivity problems or incorrect server URL configuration can prevent successful API calls.

  • Error messages and resolutions:

    • 404 Not Found: Verify the queue ID is correct and exists.
    • 412 Precondition Failed: Check the ETag value; ensure it matches the current version of the queue.
    • Authentication errors: Confirm that the API key credential is valid and has sufficient permissions.

Links and References

Discussion