3CX icon

3CX

Interact with 3CX telephony system
Join our community

Actions462

Overview

This node interacts with the 3CX telephony system, specifically focusing on managing Service Principals. The "Generate App Token" operation allows users to generate an application token for a given service principal by specifying its entity ID. This is useful in scenarios where automated or programmatic access tokens are needed for service principals within the 3CX environment, such as integrating third-party applications or automating telephony workflows.

Properties

Name Meaning
Id The unique identifier (entity ID) of the service principal for which the app token will be generated. This can be provided directly or dynamically via expressions like {{$json.Id}}.

Output

The node outputs JSON data containing the result of the token generation request. Typically, this includes the generated application token and possibly related metadata about the service principal or token validity. The exact structure depends on the 3CX API response but generally provides the necessary token information for subsequent authenticated requests.

No binary data output is indicated.

Dependencies

  • Requires an active connection to a 3CX telephony system.
  • Needs an API authentication credential configured in n8n (an OAuth2-based API key credential).
  • The base URL for the 3CX API must be set in the credentials configuration.
  • The node sends requests to the /xapi/v1 endpoint of the 3CX server.

Troubleshooting

  • Invalid or missing Id: Ensure that the "Id" property is correctly set and corresponds to an existing service principal entity in 3CX.
  • Authentication errors: Verify that the API authentication token/credential is valid and has sufficient permissions.
  • Network issues: Confirm that the 3CX server URL is reachable from the n8n instance.
  • API errors: If the 3CX API returns errors, check the error message for details such as rate limits, invalid parameters, or expired credentials.

Links and References

Discussion