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 receptionist entity. It is useful in scenarios where you need to programmatically remove receptionist records from your 3CX system, such as automating cleanup tasks or managing user roles dynamically.

For example, if you have a workflow that processes employee offboarding, this node can be used to delete the corresponding receptionist entry in 3CX automatically.

Properties

Name Meaning
Id The unique identifier of the receptionist entity to delete. Can be set using expressions like {{$json.Id}}. This property is required.
If Match An optional ETag value for concurrency control. Used as an HTTP header 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 any relevant status information returned by the 3CX API. There is no indication that binary data is output by this node.

Dependencies

  • Requires an API authentication token credential to connect securely to the 3CX system.
  • Needs the base URL of the 3CX server configured in the credentials.
  • The node sends requests to the 3CX API endpoint /xapi/v1.

Troubleshooting

  • Invalid or missing Id: Ensure the Id property is provided and correctly references an existing receptionist entity.
  • ETag mismatch error: If using the If Match header, a mismatch indicates the resource was modified since last fetched. Refresh the ETag value before retrying.
  • Authentication errors: Verify that the API key or OAuth2 token 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