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 holiday entry from the system's holiday list. Deleting holidays can be useful for administrators who need to update or correct the holiday schedule used in call routing or other telephony features.

A practical example is when a company removes a previously scheduled holiday and wants to ensure that the telephony system no longer treats that day as a holiday, thus restoring normal call handling on that date.

Properties

Name Meaning
Id The unique identifier of the holiday entity to delete. Can be set using an expression like {{$json.Id}}. This is required.
If Match Optional ETag header value used for concurrency control. It ensures the holiday 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 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 telephony system.
  • The node expects the base URL of the 3CX server to be configured in the credentials.
  • The node sends HTTP requests to the 3CX API endpoint /xapi/v1.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent holiday Id will cause the deletion to fail.
    • Missing or incorrect API authentication credentials will prevent the node from connecting to the 3CX server.
    • Using an outdated ETag value in the "If Match" property may cause the request to be rejected due to concurrency conflicts.

  • Error messages:

    • 404 Not Found: The specified holiday Id does not exist.
    • 401 Unauthorized: Authentication failed; check API credentials.
    • 412 Precondition Failed: The ETag provided in "If Match" does not match the current version of the resource.

To resolve these errors, verify the holiday Id, ensure valid API credentials are configured, and use the latest ETag value if concurrency control is needed.

Links and References

Discussion