Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with an Active Directory service via the Connect Secure API to retrieve detailed information about a specific computer object. It is designed to fetch computer details based on unique identifiers and query parameters, making it useful in IT management, asset tracking, or security auditing scenarios where detailed computer metadata from Active Directory is required.

Practical examples include:

  • Fetching detailed attributes of a computer by its GUID for inventory purposes.
  • Querying computers filtered by certain conditions or ordering criteria.
  • Paginating through large sets of computer records using skip and limit parameters.

Properties

Name Meaning
Company Id Numeric identifier representing the company context for the query.
Object Guid Unique string identifier (GUID) of the computer object 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 query condition string to filter results based on specific criteria.
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 detailed information of the requested computer objects retrieved from Active Directory. The structure typically includes all relevant attributes associated with the computer entity as provided by the API response.

If binary data were involved (not indicated here), it would represent files or attachments related to the computer details, but this node focuses on JSON metadata output.

Dependencies

  • Requires an active connection to the Connect Secure API.
  • Needs an API authentication token or key configured in n8n credentials to authorize requests.
  • The node sends HTTP queries with parameters and headers as specified by the input properties.

Troubleshooting

  • Missing or invalid credentials: Ensure that the API key or authentication token is correctly set up in n8n credentials.
  • Invalid Object Guid: If the GUID does not correspond to any computer object, the API may return an error or empty result.
  • Incorrect query parameters: Invalid values for company_id, source, or malformed condition strings can cause request failures.
  • Pagination issues: Setting skip or limit incorrectly might lead to unexpected empty results or incomplete data.
  • Header issues: The X USER ID header must be provided and valid; otherwise, the API may reject the request.

To resolve errors, verify all required fields are correctly filled, check API documentation for valid parameter formats, and ensure network connectivity to the API endpoint.

Links and References

Discussion