3CX icon

3CX

Interact with 3CX telephony system

Actions462

Overview

This node interacts with the "My User" resource to list the groups that the current user belongs to. It is useful in scenarios where you need to retrieve and manage user group memberships, such as for access control, reporting, or synchronization purposes. For example, an administrator might use this node to fetch all groups a user is part of before assigning permissions or sending notifications.

Properties

Name Meaning
Options A collection of optional query parameters to customize the list of user groups returned:
$top Show only the first n items
$skip Skip the first n items
$search Search items by search phrases. If the search phrase contains spaces and is not quoted, it will be automatically quoted.
$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)

Output

The node outputs JSON data representing the list of user groups associated with the current user. The structure typically includes an array of group objects, each containing properties as specified or filtered by the input options. If the $count option is enabled, the output may also include the total count of matching groups.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key or OAuth2 authentication token configured in n8n credentials to authenticate requests.
  • Depends on the external service's API endpoint that provides user group information.
  • The base URL for API requests is dynamically set from the credential configuration.

Troubleshooting

  • Common issues:
    • Authentication failures due to missing or invalid API credentials.
    • Incorrect query parameter syntax causing API errors.
    • Empty results if filters or search terms do not match any groups.
  • Error messages:
    • Authorization errors: Verify that the API key or OAuth2 token is correctly configured and has sufficient permissions.
    • Bad request errors: Check the formatting of filter, search, and other query parameters.
    • Network errors: Ensure the API server URL is correct and reachable.

Links and References

  • Refer to the external API documentation for detailed descriptions of query parameters like $filter, $search, $orderby, etc.
  • Consult n8n documentation on setting up API credentials and using HTTP request nodes for similar integrations.

Discussion