AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node interacts with the AvantGuard ConnectSecure API to retrieve asset security report data. Specifically, it supports an operation to get detailed security reports for assets by querying the API with user identification and optional filtering parameters. This is useful in scenarios where users need to programmatically access security insights or audit information about their assets, such as in automated security monitoring, compliance reporting, or integration with other IT management tools.

For example, a security analyst could use this node to fetch recent vulnerability reports on specific assets filtered by conditions like date ranges or severity levels, enabling automated alerting or dashboard updates.

Properties

Name Meaning
X USER ID The User Id header value required to authenticate or identify the user making the request.
Additional Query Parameters Optional query parameters to refine the data retrieval:
- Condition: A query condition string to filter results.
- 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 asset security report retrieved from the API. The structure corresponds to the API's response schema for asset security reports, typically including details such as asset identifiers, security findings, timestamps, and related metadata.

No binary data output is indicated.

Dependencies

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

Troubleshooting

  • Missing or invalid X USER ID: The node requires the "X USER ID" header; omitting or providing an incorrect value will likely cause authentication or authorization errors.
  • Invalid query parameters: Providing malformed or unsupported query conditions may result in API errors or empty responses.
  • API connectivity issues: Ensure the base URL and API credentials are correctly set and that the network allows outbound requests to the AvantGuard API.
  • Pagination mishandling: Using skip and limit incorrectly might lead to unexpected subsets of data; verify these values carefully.

Links and References

  • AvantGuard ConnectSecure API documentation (refer to your organization's API docs)
  • n8n documentation on creating custom nodes and using API credentials
  • OpenAPI Specification: https://swagger.io/specification/

Discussion