Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation, Retrieve Ad Ous View, is designed to query and retrieve Organizational Units (OUs) from an Active Directory service. It allows users to specify filtering conditions, pagination controls, and sorting options to customize the data retrieval. This operation is useful in scenarios where you need to programmatically access and manage directory structures within an enterprise environment, such as syncing AD OUs with other systems, auditing organizational hierarchy, or building custom reports.

Practical examples include:

  • Fetching a subset of OUs based on specific attributes or conditions.
  • Paginating through large sets of OUs to process them in batches.
  • Ordering the results by certain fields like name or creation date.

Properties

Name Meaning
X USER ID User Id header value required for authentication or identification in the request.
Condition Query condition string to filter which OUs to retrieve (e.g., LDAP filter syntax).
Skip Number of records to skip, used for pagination.
Limit Maximum number of records to return, used for pagination.
Order By Field(s) to order the results by (e.g., "name asc", "createdDate desc").

Output

The output of this operation is JSON data representing the retrieved Active Directory Organizational Units matching the specified query parameters. Each item in the output typically contains details about an OU such as its distinguished name, attributes, and possibly metadata depending on the API response.

If binary data were involved (not indicated here), it would represent files or attachments related to the OUs, but this operation focuses on JSON structured data only.

Dependencies

  • Requires an API key credential or similar authentication token configured in n8n to authorize requests against the Active Directory API.
  • The node depends on the external Active Directory service's API endpoint that supports querying OUs with filtering, pagination, and ordering.
  • No additional environment variables are explicitly required beyond standard API credentials.

Troubleshooting

  • Missing or invalid X USER ID: The operation requires a valid user identifier header; ensure this is provided and correct.
  • Invalid query condition syntax: If the condition string is malformed or unsupported by the API, the request may fail or return no results. Validate the query format according to the Active Directory API documentation.
  • Pagination issues: Setting skip or limit incorrectly might result in empty responses or incomplete data. Verify these values align with expected dataset size.
  • Order By errors: Using unsupported fields or incorrect syntax in the order_by parameter can cause errors or ignored sorting.
  • Authentication failures: Ensure the API key or authentication token is valid and has sufficient permissions to read OUs.

Links and References

Discussion