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 an inbound rule by its unique identifier. Deleting inbound rules is useful for managing call routing configurations dynamically, such as removing outdated or incorrect rules that control how incoming calls are handled.

A practical example would be automating the cleanup of inbound rules when certain conditions are met, like disabling call forwarding during off-hours or after a campaign ends.

Properties

Name Meaning
Id The unique identifier of the inbound rule to delete. Can be set using expressions like {{$json.Id}}. This is required.
If Match Optional ETag header value used for concurrency control. It ensures the rule is deleted only if it matches the specified version.

Output

The node outputs JSON data representing the result of the delete operation. Typically, this will include confirmation of deletion or relevant status information from the 3CX API. There is no indication that binary data is returned.

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 /xapi/v1 endpoint of the 3CX server.

Troubleshooting

  • Invalid or missing Id: Ensure the Id property is provided and correctly references an existing inbound rule.
  • ETag mismatch error: If using the If Match header, a mismatch indicates the resource has changed since last fetched. Refresh the ETag value before retrying.
  • Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
  • Network or URL issues: Confirm the 3CX server URL is correct and accessible from n8n.

Links and References

Discussion