3CX icon

3CX

Interact with 3CX telephony system

Actions462

Overview

This node interacts with the 3CX telephony system, specifically providing functionality related to backups. The "Get Backup Extras" operation retrieves additional information or metadata associated with a specific backup file in the 3CX system. This can be useful for administrators who need to inspect details about backup files, such as their contents or supplementary data, without restoring the entire backup.

Practical examples include:

  • Fetching metadata about a backup before deciding whether to restore it.
  • Automating backup management by retrieving extra details to log or audit backup files.
  • Integrating backup information into broader IT workflows or dashboards.

Properties

Name Meaning
File Name The key or identifier of the backup file whose extra information is to be retrieved. Supports expressions, e.g., {{$json.FileName}}.

Output

The node outputs JSON data containing the extra information related to the specified backup file. This typically includes metadata or additional details that describe or supplement the backup. The exact structure depends on the 3CX API response but generally provides insight into the backup's contents or attributes.

If the node supports binary data output (not evident from the provided code), it would represent actual backup file content or related binary attachments; however, this is not indicated here.

Dependencies

  • Requires an API authentication token credential to connect securely to the 3CX telephony system.
  • Needs the base URL of the 3CX server configured in the credentials.
  • Relies on the 3CX REST API endpoint /xapi/v1 for communication.

Troubleshooting

  • Common issues:

    • Invalid or missing file name property will cause the operation to fail.
    • Incorrect or expired API authentication token may result in authorization errors.
    • Misconfigured server URL can lead to connection failures.
  • Error messages and resolutions:

    • "Unauthorized" or "Authentication failed": Verify that the API authentication token is valid and has not expired.
    • "File not found": Check that the provided file name matches an existing backup file.
    • "Network error": Ensure the server URL is correct and reachable from the n8n instance.

Links and References

Discussion