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 website link (weblink) associated with their 3CX setup. The "Delete Weblink" operation removes a specified weblink identified by its key. This is useful for managing and cleaning up links that are no longer needed or valid within the 3CX environment.

Practical examples include:

  • Automatically removing outdated or invalid weblinks from your 3CX system as part of a workflow.
  • Managing weblinks dynamically based on external triggers or data changes.

Properties

Name Meaning
Link The unique key identifying the weblink to delete. Supports expressions, e.g., {{$json.Link}}.
If Match Optional ETag header value used for conditional deletion to ensure the resource has not changed.

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 authentication token credential to connect securely to the 3CX system.
  • The base URL for the 3CX API must be configured in the node credentials.
  • The node sends HTTP requests to the 3CX API endpoint /xapi/v1.

Troubleshooting

  • Common issues:

    • Providing an incorrect or non-existent Link key will result in failure to delete the weblink.
    • Missing or invalid API credentials will cause authentication errors.
    • Using an outdated or incorrect ETag value in the "If Match" property may lead to a precondition failure, preventing deletion.

  • Error messages:

    • 404 Not Found: The specified weblink 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 Link key is correct and exists.
  • Ensure valid API credentials are configured.
  • Use the latest ETag value when using the "If Match" header.

Links and References

Discussion