AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node interacts with the AvantGuard ConnectSecure API to retrieve information about asset Windows compatibility for a company. It is designed to fetch data related to how Windows assets are compatible within a company's environment, which can be useful for IT administrators or security teams managing endpoint compatibility and compliance.

Typical use cases include:

  • Auditing Windows asset compatibility across an organization.
  • Integrating asset compatibility data into broader IT management workflows.
  • Filtering and sorting asset compatibility records based on specific conditions.

Properties

Name Meaning
X USER ID User identifier required for authentication or tracking of the request.
Additional Query Parameters Optional parameters to refine the query results:
- Condition: Filter condition for querying records.
- Skip: Number of records to skip (for pagination).
- Limit: Maximum number of records to return.
- Order By: Field(s) to order the results by.

Output

The node outputs JSON data representing the retrieved Windows asset compatibility information for the specified company. The structure typically includes details about each asset's compatibility status and related metadata as returned by the API.

No binary data output is indicated in the source code.

Dependencies

  • Requires an API key credential for AvantGuard ConnectSecure service.
  • Needs the base URL of the AvantGuard ConnectSecure API configured in credentials.
  • Uses the @avantguardllc/n8n-openapi-node package and an OpenAPI specification (openapi.json) bundled with the node for request building.

Troubleshooting

  • Missing or invalid X USER ID: The node requires a valid user ID header; ensure this is provided and correct.
  • API authentication errors: Verify that the API key credential is correctly set up and has necessary permissions.
  • Query parameter issues: Incorrect or malformed query parameters (e.g., non-numeric values for skip/limit) may cause errors.
  • Network or connectivity problems: Ensure the base URL is reachable from the n8n instance.

Links and References

Discussion