3CX icon

3CX

Interact with 3CX telephony system
Join our community

Actions462

Overview

This node integrates with the 3CX telephony system, specifically allowing users to delete a contact from their 3CX contacts list. It is useful in scenarios where you need to programmatically manage your contact database, such as cleaning up outdated or incorrect contact entries automatically based on external triggers or workflows.

For example, if a contact is removed from a CRM system, this node can be used to ensure the corresponding contact is also deleted from the 3CX system, maintaining synchronization between platforms.

Properties

Name Meaning
Id The unique identifier of the contact to delete. You can provide this directly or via an expression (e.g., {{$json.Id}}). This is required.
If Match Optional ETag header value for concurrency control. Used to ensure the contact 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.

No binary data output is expected from this node.

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 contact ID will result in an error indicating the contact could not be found.
    • Missing or incorrect API authentication credentials will cause authorization failures.
    • Using an incorrect or stale ETag value in the "If Match" property may lead to concurrency errors preventing deletion.

  • Error messages and resolutions:

    • 404 Not Found: Verify that the contact ID exists in the 3CX system.
    • 401 Unauthorized: Check that the API key credential is correctly set and has necessary permissions.
    • 412 Precondition Failed: The ETag provided in "If Match" does not match the current version of the contact; refresh the contact data and try again without or with updated ETag.

Links and References

Discussion