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 outbound rule. Outbound rules in 3CX define how outgoing calls are routed and managed. Deleting an outbound rule can be useful when you want to remove outdated or incorrect call routing configurations.

A practical example is when a company restructures its phone system and needs to remove old call routing rules that no longer apply, ensuring calls are handled correctly according to new policies.

Properties

Name Meaning
Id The unique identifier of the outbound rule to delete. Can be set dynamically via expressions like {{$json.Id}}. Must be provided.
If Match Optional ETag header value used for concurrency control. Helps ensure 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 confirm whether the deletion was successful or provide error details if it failed.

No binary data output is expected from this operation.

Dependencies

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

Troubleshooting

  • Missing or invalid Id: Ensure the Id property is provided and corresponds to an existing outbound rule.
  • ETag mismatch: If using the If Match header, a mismatch may cause the delete to fail. Retrieve the latest ETag before attempting deletion.
  • Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
  • Network issues: Confirm connectivity to the 3CX server URL.
  • API errors: Check the response message for specific API error codes and messages.

Links and References

Discussion