3CX icon

3CX

Interact with 3CX telephony system
Join our community

Actions462

Overview

This node interacts with the 3CX telephony system, specifically allowing users to delete a playlist resource. The "Delete Playlist" operation removes a specified playlist from the 3CX system by its unique name identifier. This is useful in scenarios where playlists are no longer needed or must be refreshed, such as managing call queues or automated messaging sequences.

Practical examples include:

  • Removing outdated or obsolete call routing playlists.
  • Cleaning up test playlists created during development.
  • Automating playlist lifecycle management within a larger telephony workflow.

Properties

Name Meaning
Name The unique key (name) of the playlist to delete. Supports expressions like {{$json.Name}}.
If Match Optional ETag header value for concurrency control. Ensures the playlist is deleted only if it matches the provided ETag.

Output

The node outputs JSON data representing the response from the 3CX API after attempting to delete the playlist. Typically, this will confirm successful deletion or provide error details if the operation failed.

No binary data output is expected from this operation.

Dependencies

  • Requires an API authentication token credential configured in n8n to connect securely to the 3CX server.
  • The node expects the base URL of the 3CX server to be set in the credentials.
  • The node sends requests to the 3CX REST API endpoint /xapi/v1.

Troubleshooting

  • Common issues:

    • Providing an incorrect or non-existent playlist name will result in an error indicating the playlist was not found.
    • Omitting the required API authentication token or misconfiguring the server URL will cause connection failures.
    • Using an invalid or stale ETag in the "If Match" property may lead to a concurrency error, preventing deletion.

  • Error messages and resolutions:

    • 404 Not Found: Verify that the playlist name is correct and exists on the 3CX server.
    • 401 Unauthorized: Check that the API authentication token is valid and properly configured.
    • 412 Precondition Failed: The ETag provided in "If Match" does not match the current playlist version; refresh the ETag or omit this header if concurrency control is not needed.

Links and References

Discussion