3CX icon

3CX

Interact with 3CX telephony system

Actions462

Overview

This node interacts with the 3CX telephony system, specifically allowing users to delete an address from the blocklist. It is useful in scenarios where administrators want to remove certain phone numbers or addresses from being blocked, thereby restoring their ability to communicate through the 3CX system.

For example, if a previously blocked phone number should be allowed again, this node can be used to delete that entry from the blocklist by specifying its unique identifier.

Properties

Name Meaning
Id The unique identifier of the blocklist entry to delete. Can be set dynamically via expressions like {{$json.Id}}. This is a required numeric field.
If Match Optional ETag header value for concurrency control. Used to ensure the blocklist entry has not changed since last retrieval before deletion.

Output

The node outputs JSON data representing the result of the delete operation. Typically, this will include confirmation of successful deletion or error details if the operation failed. There is no binary output associated with 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 node credentials.
  • The node sends requests to the 3CX API endpoint /xapi/v1.

Troubleshooting

  • Common issues:

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

    • "Not Found" or similar indicates the specified blocklist entry does not exist.
    • "Unauthorized" or "Forbidden" suggests issues with API credentials or permissions.
    • "Precondition Failed" may occur if the If-Match header does not match the current ETag of the resource; in this case, refresh the ETag and retry.

Links and References

Discussion