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 device information records. The "Delete Device Info" operation removes a device info entity identified by its unique ID from the 3CX system. This is useful for managing and cleaning up device records that are no longer needed or valid.

Practical examples include:

  • Removing outdated or decommissioned devices from the telephony system.
  • Automating cleanup of device records based on external triggers or workflows.
  • Managing device lifecycle within a larger communication management process.

Properties

Name Meaning
Id The unique identifier of the device info entity to delete. Can be set via expression.
If Match Optional ETag header value used for concurrency control to ensure the entity has not changed since last retrieval.

Output

The node outputs JSON data representing the result of the delete operation. Typically, this will confirm successful deletion or provide error details if the operation failed. There is no binary output associated with this operation.

Dependencies

  • Requires an API key credential for authenticating with the 3CX telephony 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 invalid or non-existent Id will cause the delete operation to fail.
    • Missing or incorrect API authentication credentials will result in authorization errors.
    • Using an outdated or incorrect If-Match ETag header may cause the request to be rejected due to concurrency conflicts.

  • Error messages:

    • 404 Not Found: The specified device info 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 entity version.

  • Resolutions:

    • Verify the device info ID exists before attempting deletion.
    • Ensure API credentials are correctly configured and valid.
    • Retrieve the latest ETag value before deleting if using the If-Match header.

Links and References

Discussion