AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node operation "Get Retrieve Ad Users View" under the "Active Directory" resource is designed to fetch user information from an Active Directory service. It allows retrieving a filtered and paginated list of AD users based on optional query parameters such as conditions, skip count, limit, and ordering. This is useful in scenarios where you need to programmatically access user details for automation workflows, reporting, or synchronization with other systems.

Practical examples include:

  • Fetching a subset of users who meet certain criteria (e.g., department equals "Sales").
  • Paginating through large user lists by skipping and limiting records.
  • Ordering users by attributes like username or creation date.

Properties

Name Meaning
X USER ID The User Id header value required for authentication or identification in the request.
Additional Query Parameters Optional parameters to refine the query:
- Condition: A filter condition string to narrow down the user search.
- Skip: Number of records to skip (for pagination).
- Limit: Maximum number of records to return.
- Order By: Field name(s) to order the results by.

Output

The node outputs JSON data representing the retrieved Active Directory users according to the query parameters specified. The structure typically includes user attributes such as usernames, IDs, and other relevant directory fields depending on the AD schema and API response.

There is no indication that this node outputs binary data.

Dependencies

  • Requires connection to an Active Directory service endpoint.
  • Needs an API key or token for authentication, passed via the X USER ID header.
  • The node depends on an OpenAPI specification (openapi.json) bundled internally to define its properties and requests.
  • Requires proper configuration of the base URL and credentials in n8n to connect to the Active Directory API.

Troubleshooting

  • Missing or invalid X USER ID header: The request will fail if the required user ID header is not provided or incorrect. Ensure this property is set correctly.
  • Invalid query parameters: Providing malformed or unsupported query conditions may result in errors or empty responses. Validate the syntax and supported fields for the condition parameter.
  • Pagination issues: Setting skip or limit incorrectly might cause unexpected results or no data returned. Use sensible values within the API limits.
  • Authentication failures: If the API key or token is expired or misconfigured, the node will not be able to retrieve data. Verify credential setup in n8n.
  • Network or connectivity problems: Ensure the Active Directory API endpoint is reachable from the n8n environment.

Links and References

Discussion