3CX icon

3CX

Interact with 3CX telephony system
Join our community

Actions462

Overview

The node interacts with the 3CX telephony system, specifically allowing users to revoke security tokens. This operation is useful in scenarios where a security token needs to be invalidated, such as when a token is compromised or no longer needed. For example, an administrator can automate the revocation of access tokens for users who have left an organization or when rotating credentials for enhanced security.

Properties

Name Meaning
Id The unique identifier of the security token entity to revoke. This is a required numeric value and can be provided directly or via an expression (e.g., {{$json.Id}}).

Output

The node outputs JSON data representing the result of the revoke operation. Typically, this would include confirmation that the token was successfully revoked or details about any errors encountered. There is no indication that the node outputs binary data.

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 node's credentials.
  • The node sends requests to the 3CX API endpoint /xapi/v1.

Troubleshooting

  • Invalid or missing Id: If the Id property is not provided or invalid, the node will likely fail to revoke the token. Ensure the Id is correctly set and corresponds to an existing security token.
  • Authentication errors: If the API key or OAuth2 credentials are incorrect or expired, the node will fail to authenticate with the 3CX API. Verify the credentials and refresh if necessary.
  • API endpoint issues: Incorrect server URL configuration may cause connection failures. Confirm the base URL is correct and accessible.
  • Permission errors: The authenticated user must have sufficient permissions to revoke security tokens; otherwise, the API will reject the request.

Links and References

Discussion