3CX icon

3CX

Interact with 3CX telephony system
Join our community

Actions462

Overview

This node integrates with the 3CX telephony system, allowing users to manage various resources within 3CX. Specifically, the "Delete Parking" operation under the "Parkings" resource enables users to delete a parking entity by its unique identifier. This is useful in scenarios where a parking slot or configuration needs to be removed from the 3CX system, such as cleaning up unused or obsolete parking spots.

Practical example: A user managing call parking slots in 3CX can automate the removal of a parking slot when it is no longer needed, ensuring the telephony system remains organized and up-to-date.

Properties

Name Meaning
Id The unique identifier of the parking entity to delete. Can be set dynamically via expressions like {{$json.Id}}. Must be a number.
If Match Optional ETag header value used for concurrency control. Helps ensure the entity has not changed since last retrieval before deletion.

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. There is no indication that binary data is output by this node.

Dependencies

  • Requires an API key credential for authenticating with the 3CX telephony system.
  • The base URL for the 3CX API must 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 parking ID will likely result in an error response from the API.
    • Missing or incorrect API authentication credentials will cause authorization failures.
    • Using an outdated ETag value in the "If Match" property may lead to concurrency errors if the resource has been modified since the ETag was obtained.

  • Error messages:

    • Authorization errors indicate problems with the API key or token; verify credentials.
    • Not found errors suggest the specified parking ID does not exist.
    • Precondition failed errors relate to ETag mismatches; refresh the ETag before retrying.

Links and References

Discussion