Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation, Retrieve Ad Group Computers under the Active Directory resource, is designed to fetch computer objects that belong to a specific Active Directory group. It queries an external API (likely a Connect Secure API) to retrieve details about computers associated with a given AD group identified by its Object GUID.

Typical use cases include:

  • Automating inventory or audit processes by listing all computers in a particular AD group.
  • Integrating AD group membership data into IT management workflows.
  • Filtering and managing devices based on group membership for security or compliance purposes.

For example, an IT admin could use this node to get all computers in the "Finance Department" AD group to apply specific policies or monitor their status.

Properties

Name Meaning
Company Id Numeric identifier of the company context for the query.
Object Guid The unique identifier (GUID) of the Active Directory group whose computers are retrieved.
X USER ID User identifier sent as a header for authentication or tracking purposes.
Condition Optional query condition to filter results further.
Skip Number of records to skip in the result set (for pagination).
Limit Maximum number of records to return (for pagination).
Order By Field name(s) to order the results by.

Output

The node outputs JSON data representing the list of computers retrieved from the specified AD group. Each item in the output typically contains properties describing a computer object, such as its name, identifiers, and possibly other metadata returned by the API.

If the API supports binary data (e.g., computer-related files or certificates), it would be included in the binary output field, but based on the provided code and properties, the primary output is structured JSON data.

Dependencies

  • Requires an API key credential for authenticating requests to the Connect Secure API or equivalent service.
  • The node depends on the external API endpoint that provides Active Directory group computer information.
  • Proper configuration of the API credentials and network access to the API endpoint is necessary.

Troubleshooting

  • Missing or invalid credentials: Ensure the API key or authentication token is correctly configured in n8n credentials.
  • Invalid Object GUID: If the Object Guid does not correspond to a valid AD group, the API may return errors or empty results.
  • Pagination issues: Incorrect values for skip and limit might cause unexpected result sets; verify these parameters.
  • API rate limits or connectivity problems: Network issues or API throttling can cause request failures.
  • Header misconfiguration: The X USER ID header must be correctly set; missing or incorrect values may lead to authorization errors.

Common error messages might include unauthorized access, resource not found, or bad request due to malformed parameters. Checking the input parameters and credentials usually resolves these.

Links and References

Discussion