3CX icon

3CX

Interact with 3CX telephony system
Join our community

Actions462

Overview

The node provides an operation to delete a CRM Template by its unique identifier (Name). This is useful in scenarios where you need to programmatically remove outdated or unwanted CRM templates from the 3CX telephony system, helping maintain an organized and up-to-date template repository. For example, if a marketing team updates their campaign templates regularly, this node can automate the cleanup of old templates.

Properties

Name Meaning
Name The unique key (Name) of the CRM Template to delete. Supports expressions like {{$json.Name}}.
If Match Optional ETag header value for concurrency control. Used to ensure the template has not changed since last retrieval before deletion.

Output

The output JSON typically contains the response from the API after attempting to delete the specified CRM Template. It may include status information or confirmation of deletion. There is no indication that binary data is returned by this operation.

Dependencies

  • Requires an API authentication token credential to connect securely to the 3CX telephony system.
  • The base URL for the 3CX API must be configured in the node credentials.
  • The node sends HTTP requests with JSON headers and expects JSON responses.

Troubleshooting

  • Common issues:

    • Deletion fails if the specified template Name does not exist.
    • If the "If Match" ETag header is provided but does not match the current template version, the deletion will be rejected to prevent accidental removal of updated templates.
    • Network or authentication errors if the API credentials or server URL are misconfigured.

  • Error messages:

    • 404 Not Found: The template with the given Name was not found.
    • 412 Precondition Failed: The ETag provided in "If Match" does not match the current resource version.
    • 401 Unauthorized: Invalid or missing API authentication token.

To resolve these, verify the template Name exists, use the correct ETag if concurrency control is needed, and ensure valid API credentials and server URL are set.

Links and References

Discussion