Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation, "Retrieve Get Ous Details" under the "Active Directory" resource, is designed to fetch details about Organizational Units (OUs) from an Active Directory service. It allows users to query and retrieve OU information based on specific identifiers and filtering criteria.

Typical use cases include:

  • Integrating Active Directory OU data into workflows for user management or auditing.
  • Automating synchronization of organizational structure data with other systems.
  • Filtering and retrieving subsets of OUs based on conditions, pagination, and sorting preferences.

For example, a workflow could use this node to get all OUs under a particular company ID, filter them by certain attributes, and then process or display that data elsewhere.

Properties

Name Meaning
Company Id Numeric identifier representing the company whose OUs are being queried.
Object Guid String representing the unique GUID of the object in Active Directory to retrieve details for.
Source String indicating the source system or context for the query.
X USER ID User identifier sent as a header to authenticate or track the request.
Condition Optional string to specify additional query conditions or filters.
Skip Number of records to skip, used for pagination.
Limit Maximum number of records to return, used for pagination.
Order By String specifying the field(s) to order the results by.

Output

The node outputs JSON data containing the details of the requested Organizational Units. The exact structure depends on the API response but typically includes fields describing each OU's properties such as name, GUID, parent OU, and other metadata.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authentication to the Connect Secure API.
  • Depends on the external Connect Secure API endpoint that provides Active Directory OU details.
  • Proper configuration of the API credentials within n8n is necessary for successful requests.

Troubleshooting

  • Missing or invalid credentials: Ensure the API key or authentication token is correctly configured in n8n.
  • Invalid or missing required parameters: The company_id, object_guid, source, and X USER ID are mandatory; missing these will cause errors.
  • API rate limits or connectivity issues: Network problems or API throttling may result in failed requests.
  • Incorrect query conditions or ordering: Malformed condition or order_by strings might lead to empty or error responses.

Common error messages likely relate to authentication failures, invalid parameters, or server errors from the API. Verifying input values and credentials usually resolves these.

Links and References

Discussion