Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation, Retrieve Ad User Licenses, is designed to fetch license information for a specific Active Directory user. It is useful in scenarios where you need to audit or manage user licenses within an organization's Active Directory environment. For example, an IT administrator might use this node to retrieve all licenses assigned to a particular user to verify compliance or prepare reports.

Properties

Name Meaning
X USER ID The unique identifier of the Active Directory user whose licenses are to be retrieved.
Condition A query condition to filter the licenses returned (e.g., filtering by license type).
Skip Number of records to skip in the result set, useful for pagination.
Limit Maximum number of license records to return.
Order By Specifies the order in which the license records should be sorted in the response.

Output

The output contains JSON data representing the licenses associated with the specified Active Directory user. Each item in the output corresponds to a license record and includes details such as license type, status, and any other relevant metadata provided by the API.

If the node supports binary data output, it would typically represent attachments or license documents; however, based on the provided code and properties, this operation focuses on JSON data only.

Dependencies

  • Requires an active connection to the Connect Secure API that exposes Active Directory license information.
  • An API key or authentication token credential must be configured in n8n to authorize requests.
  • The node relies on the external Connect Secure service's API endpoint for Active Directory user license retrieval.

Troubleshooting

  • Missing or invalid X USER ID: The operation requires a valid user ID. Ensure the "X USER ID" property is correctly set; otherwise, the API may return errors or empty results.
  • API authentication errors: If credentials are not properly configured or expired, the node will fail to authenticate. Verify the API key/token and update if necessary.
  • Query parameter issues: Incorrectly formatted conditions or unsupported query parameters may cause the API to reject the request. Validate the syntax and supported filters.
  • Pagination mishandling: Using skip and limit incorrectly can lead to missing or duplicated records. Adjust these values carefully when processing large datasets.

Links and References

Discussion