3CX icon

3CX

Interact with 3CX telephony system
Join our community

Actions462

Overview

This node interacts with the 3CX telephony system, specifically allowing users to delete a Call Flow App by its unique identifier. It is useful in scenarios where you need to programmatically manage call flow applications within 3CX, such as cleaning up unused or obsolete call flows, automating maintenance tasks, or integrating 3CX management into broader workflows.

For example, if you have a list of Call Flow Apps that need to be removed based on certain criteria, this node can be used to delete each app by specifying its ID, streamlining administrative operations.

Properties

Name Meaning
Id The unique numeric identifier of the Call Flow App to delete. Can be set via expression.
If Match Optional ETag header value for concurrency control. Used to ensure the resource 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 by 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 system.
  • The node expects a base URL for the 3CX server, configured in the credentials.
  • The node sends requests to the 3CX REST API endpoint /xapi/v1.
  • Proper permissions on the 3CX system are necessary to delete Call Flow Apps.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent Call Flow App ID will likely result in an error from the API.
    • Missing or incorrect API authentication credentials will cause authorization failures.
    • Using an outdated or incorrect ETag value in the "If Match" property may lead to concurrency errors (e.g., HTTP 412 Precondition Failed).
    • Network connectivity issues to the 3CX server will prevent successful API calls.

  • Error messages and resolutions:

    • Unauthorized / Authentication failed: Verify that the API key credential is correctly configured and has sufficient permissions.
    • Not Found / Resource does not exist: Confirm the Call Flow App ID is correct and exists.
    • Precondition Failed: Update the "If Match" ETag value to match the current resource version or omit it if concurrency control is not needed.
    • Network errors: Check network connectivity and the correctness of the 3CX server URL.

Links and References

Discussion