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 phone logo files stored in the system. The "Delete Phone Logo" operation removes a specified phone logo by its filename. This is useful for managing and cleaning up custom branding assets within 3CX, such as removing outdated or incorrect logos.

Practical examples include:

  • Automatically deleting obsolete phone logos during a branding update workflow.
  • Removing logos that are no longer needed to free up storage or maintain organization.

Properties

Name Meaning
Filename The name of the phone logo file to delete. Supports expressions, e.g., {{$json.Filename}}.
If Match Optional ETag header value used for concurrency control to ensure the resource has not changed since last retrieval.

Output

The node outputs JSON data representing the result of the delete operation. Typically, this will confirm whether the deletion was successful or provide error details if it failed.

No binary data output is expected from 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 sends HTTP requests to the 3CX API endpoint /xapi/v1.

Troubleshooting

  • Common issues:

    • Providing an incorrect or non-existent filename will cause the delete operation to fail.
    • Missing or invalid authentication credentials will prevent the request from succeeding.
    • Using an outdated ETag value in the "If Match" property may cause a conflict error if the resource has been modified since the ETag was obtained.

  • Error messages:

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

To resolve these errors:

  • Verify the filename is correct and exists on the 3CX server.
  • Ensure valid API credentials are configured.
  • Update the ETag value before attempting deletion if using the "If Match" header.

Links and References

Discussion