AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Active Directory → Get Retrieve Ad Group Computers

AI-generated

Overview

This node operation retrieves the list of computers that belong to a specific Active Directory (AD) group. It is useful in scenarios where you need to programmatically access and manage AD group memberships, such as auditing group members, synchronizing group data with other systems, or automating IT workflows involving user and computer management.

For example, an IT administrator could use this node to fetch all computers associated with a particular AD group to verify compliance or to trigger further automation like software deployment or security scans on those machines.

Properties

Name Meaning
Company Id The identifier of the company within which the AD group exists.
Object Guid The unique GUID of the AD group whose computers are being retrieved.
X USER ID The user identifier for authentication or tracking purposes in the request header.
Additional Query Parameters Optional parameters to refine the query:
- Condition: Filter condition string
- Skip: Number of records to skip
- Limit: Maximum number of records to return
- Order By: Field(s) to order the results by

Output

The output JSON contains the list of computers that are members of the specified AD group. Each item typically includes details about a computer object in Active Directory, such as its name, identifier, and possibly other attributes depending on the API response.

If the node supports binary data output, it would represent any associated files or attachments related to the computers, but based on the provided code and properties, the primary output is structured JSON data representing AD group computers.

Dependencies

  • Requires an API key credential for authentication to the AvantGuard ConnectSecure service.
  • Needs the base URL of the AvantGuard ConnectSecure API configured in the node credentials.
  • The node uses the @avantguardllc/n8n-openapi-node package and an OpenAPI specification (openapi.json) bundled internally to build requests.

Troubleshooting

  • Missing or invalid credentials: Ensure the API key and base URL are correctly set in the node credentials; otherwise, authentication will fail.
  • Invalid Company Id or Object Guid: Providing incorrect identifiers will result in no data or errors from the API. Verify these values before running the node.
  • Query parameter issues: Incorrectly formatted or unsupported query parameters may cause the API to reject the request. Use only supported parameters as defined.
  • Network or API errors: Check network connectivity and API availability if requests time out or fail unexpectedly.

Links and References

Discussion