Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation, Retrieve Asset Installed Drivers, is designed to fetch information about installed drivers on assets from an external system via an API. It is useful in IT asset management scenarios where you need to audit or monitor the software components (drivers) installed on hardware assets. For example, a user might want to retrieve all installed drivers for a set of computers to verify compliance or troubleshoot hardware issues.

Properties

Name Meaning
X USER ID User identifier required for authentication or tracking purposes in the API request header.
Condition Query condition string to filter the results based on specific criteria.
Skip Number of records to skip in the result set, useful for pagination.
Limit Maximum number of records to return, controlling the size of the response.
Order By Field name(s) to order the results by, allowing sorted output.

Output

The node outputs JSON data representing the list of installed drivers retrieved from the asset management system. Each item in the output array corresponds to a driver record with its associated details as provided by the API. The structure depends on the external API's response schema but typically includes driver names, versions, installation dates, and related metadata.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Connect Secure API.
  • The node relies on the external Connect Secure API endpoint that provides asset driver data.
  • Proper configuration of the API credentials within n8n is necessary for successful execution.

Troubleshooting

  • Missing or invalid X USER ID: Since the X USER ID header is mandatory, omitting it or providing an incorrect value will likely cause authentication errors or empty responses.
  • Invalid query parameters: Incorrectly formatted condition, skip, limit, or order_by values may lead to API errors or unexpected results.
  • API connectivity issues: Network problems or misconfigured credentials can cause request failures.
  • Empty results: If no drivers match the query conditions, the output will be empty; verify the correctness of the condition parameter.

Links and References

Discussion