Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the "Asset Data" resource to retrieve information about an installed driver on a specific asset. It is useful in scenarios where you need to programmatically fetch details about drivers installed on hardware assets, such as for inventory management, compliance checks, or troubleshooting device configurations.

For example, you might use this node to:

  • Automatically gather driver details for assets in your IT environment.
  • Integrate asset driver data into a CMDB (Configuration Management Database).
  • Trigger alerts or workflows based on specific driver versions or statuses.

Properties

Name Meaning
X USER ID User Id required for authentication or identification purposes when making the request.
Id Numeric identifier of the asset whose installed driver information you want to retrieve.

Output

The node outputs JSON data containing the details of the installed driver for the specified asset. The exact structure depends on the API response but typically includes fields such as driver name, version, installation date, and related metadata.

No binary data output is indicated by the source code.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • The node depends on the external Connect Secure API service to fetch asset driver data.
  • Proper configuration of the API credentials within n8n is necessary for successful execution.

Troubleshooting

  • Missing or invalid X USER ID: Ensure that the "X USER ID" property is correctly set; otherwise, the API may reject the request.
  • Invalid asset Id: Providing an incorrect or non-existent asset Id will likely result in an error or empty response.
  • API authentication errors: Verify that the API key credential is valid and has sufficient permissions.
  • Network issues: Connectivity problems to the Connect Secure API endpoint can cause failures.
  • Unexpected API responses: If the API changes or returns unexpected data, the node may not parse the output correctly.

Links and References

Discussion