3CX icon

3CX

Interact with 3CX telephony system

Actions462

Overview

This node integrates with the 3CX telephony system, specifically providing an operation to delete multiple user greetings in bulk. It is useful in scenarios where administrators need to manage voicemail or greeting files for multiple users efficiently, such as cleaning up outdated greetings or removing unwanted audio files from the system.

For example, if a company updates its voicemail greetings and wants to remove old ones for several users at once, this node can be used to specify the filenames and corresponding IDs of the greetings to delete them in a single operation.

Properties

Name Meaning
Filename The name of the greeting file(s) to delete. This should correspond to the actual filename stored in the 3CX system.
Ids A JSON array containing the IDs of the greetings to delete. These IDs uniquely identify each greeting within the system.

Output

The node outputs data in JSON format representing the result of the multi-delete operation. This typically includes confirmation of which greetings were successfully deleted or any errors encountered during the process.

No binary data output is indicated by the source code.

Dependencies

  • Requires an API key credential for authenticating with the 3CX telephony system.
  • The node expects the base URL of the 3CX server to be configured in the credentials.
  • The node sends requests to the 3CX API endpoint /xapi/v1.

Troubleshooting

  • Invalid or missing credentials: Ensure that the API authentication token or OAuth2 credentials are correctly set up and have sufficient permissions to delete greetings.
  • Incorrect filename or IDs: Verify that the filenames and IDs provided match those existing in the 3CX system; otherwise, the deletion will fail or no greetings will be removed.
  • Network issues or incorrect server URL: Confirm that the 3CX server URL is correct and accessible from the n8n instance.
  • Malformed JSON in IDs property: Since the IDs property expects a JSON array, ensure it is properly formatted to avoid parsing errors.

Links and References

Discussion