3CX icon

3CX

Interact with 3CX telephony system
Join our community

Actions462

Overview

This node interacts with the 3CX telephony system, specifically providing an operation to list the rights associated with "My Group". It is useful for scenarios where you need to retrieve and manage permissions or access rights assigned to a particular group within the 3CX environment. For example, administrators can use this node to audit group permissions or dynamically adjust workflows based on group rights.

Properties

Name Meaning
Options A collection of query parameters to customize the request:
- Top: Show only the first n items
- Skip: Skip the first n items
- Search: Search items by search phrases (supports phrase quoting automatically)
- Filter: Filter items by property values (e.g., State eq 'Connected')
- Count: Include count of items (boolean)
- Orderby: Order items by property values (e.g., Name desc, CreatedAt asc)
- Select: Select specific properties to be returned (e.g., Id,Name)
- Expand: Expand related entities (e.g., RelatedEntity1,RelatedEntity2)

These options allow fine-grained control over the data retrieved from the "My Group Rights" endpoint.

Output

The node outputs JSON data representing the list of rights associated with "My Group". The structure typically includes details about each right, such as identifiers, names, states, or other relevant metadata depending on the API response. If binary data were involved, it would be summarized here, but in this case, the output is purely JSON.

Dependencies

  • Requires an API key credential for authenticating with the 3CX telephony system.
  • The node expects a base URL for the 3CX server, configured in the credentials.
  • No additional external dependencies are indicated.

Troubleshooting

  • Common Issues:

    • Incorrect or missing API authentication token will cause authorization errors.
    • Malformed filter or query parameters may result in API errors or empty responses.
    • Network connectivity issues to the 3CX server can cause timeouts or failures.

  • Error Messages:

    • Authorization errors typically indicate invalid or expired credentials; re-authenticate or update the API key.
    • Query parameter errors suggest syntax mistakes in filters or search strings; verify the format matches API expectations.
    • Connection errors require checking network settings and server availability.

Links and References

Discussion