3CX icon

3CX

Interact with 3CX telephony system
Join our community

Actions462

Overview

The node interacts with the 3CX telephony system, specifically allowing users to delete backup files stored in the system. This operation is useful for managing storage by removing outdated or unnecessary backup files programmatically within an n8n workflow. For example, a user might automate cleanup of backups older than a certain date or remove backups after successful restoration.

Properties

Name Meaning
File Name The name of the backup file to delete. Supports expressions, e.g., {{$json.FileName}}.
If Match Optional ETag header value used for concurrency control to ensure the backup has not changed since last retrieval.

Output

The node outputs JSON data representing the result of the delete operation. Typically, this will include confirmation of deletion or relevant status information returned from the 3CX API. 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 requests to the 3CX API endpoint /xapi/v1.

Troubleshooting

  • Common issues:

    • Incorrect or missing "File Name" property will cause the delete operation to fail.
    • Providing an invalid or stale ETag in the "If Match" header may result in a concurrency error (e.g., HTTP 412 Precondition Failed).
    • Network or authentication errors if the API key or server URL is misconfigured.

  • Error messages:

    • 404 Not Found: The specified backup file does not exist.
    • 401 Unauthorized: Authentication failed due to invalid credentials.
    • 412 Precondition Failed: The ETag provided in "If Match" does not match the current version of the backup file.

To resolve these errors, verify the file name, ensure correct and up-to-date ETag values, and confirm that API credentials and server URLs are correctly set.

Links and References

Discussion