AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node is designed to retrieve detailed information about a specific computer object from an Active Directory service. It is particularly useful in scenarios where you need to fetch attributes or metadata of a computer identified by its unique Object GUID within a given company context. For example, IT administrators can use this node to automate the retrieval of computer details for inventory management, auditing, or compliance reporting.

Properties

Name Meaning
Company Id Numeric identifier representing the company under which the Active Directory query is made.
Object Guid The unique identifier (GUID) of the computer object whose details are being retrieved.
Source The source system or domain from which the computer details should be fetched.
X USER ID User identifier used 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 node outputs JSON data containing the detailed attributes of the requested computer object from Active Directory. This typically includes all relevant properties associated with the computer as stored in the directory, such as name, status, last login, and other metadata. The output does not include binary data.

Dependencies

  • Requires an API key credential for authenticating requests to the Active Directory service.
  • Needs configuration of the base URL for the Active Directory API endpoint.
  • The node depends on an external Active Directory API that supports querying computer objects by company ID, object GUID, and source.
  • Proper user identification must be provided via the X USER ID header for authorization or audit logging.

Troubleshooting

  • Missing Required Fields: Ensure that Company Id, Object Guid, Source, and X USER ID are all provided; missing any will cause the request to fail.
  • Invalid Object GUID: If the GUID does not correspond to any computer object, the node may return an empty result or an error indicating the object was not found.
  • Authentication Errors: Verify that the API key credential is valid and has sufficient permissions to access the requested resource.
  • API Endpoint Issues: Confirm that the base URL is correctly configured and reachable from n8n.
  • Query Parameter Misuse: Incorrect values in additional query parameters like limit or skip might lead to unexpected results or errors.

Links and References

Discussion