AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node interacts with the AvantGuard ConnectSecure API to retrieve information about installed drivers on a specific asset. It is designed to fetch detailed data about the drivers installed on an asset, which can be useful for IT asset management, compliance auditing, or troubleshooting hardware/software compatibility issues.

Typical use cases include:

  • Automatically gathering driver information from assets in an enterprise environment.
  • Integrating driver inventory data into asset management systems.
  • Monitoring and reporting on driver versions and installations for compliance or update planning.

Properties

Name Meaning
X USER ID The user identifier required for authentication or tracking purposes in the API request.
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 representing the list of installed drivers retrieved from the asset. Each item in the output typically contains details such as driver name, version, installation date, and other relevant metadata provided by the API.

If binary data were involved (e.g., driver files), it would be indicated here, but this node focuses on JSON metadata output only.

Dependencies

  • Requires an API key credential for AvantGuard ConnectSecure to authenticate requests.
  • Needs the base URL of the AvantGuard ConnectSecure API configured in the node credentials.
  • Depends on the @avantguardllc/n8n-openapi-node package for building and sending API requests based on the OpenAPI specification.

Troubleshooting

  • Missing or invalid X USER ID: The API requires a valid user ID header; ensure this property is set correctly.
  • API authentication errors: Verify that the API key credential is properly configured and has necessary permissions.
  • Query parameter misuse: Incorrect values in additional query parameters (e.g., non-numeric skip/limit) may cause request failures.
  • Network or connectivity issues: Ensure the n8n instance can reach the AvantGuard API endpoint.
  • Empty or unexpected responses: Check if the asset actually has installed drivers and that the query conditions are correct.

Links and References

Discussion