AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node operation, "Get Retrieve Asset Patches Info," is designed to fetch information about patches related to assets from an external service. It is useful in scenarios where users need to query detailed patch data for specific assets, such as in IT asset management, software update tracking, or compliance auditing. For example, a user might retrieve all patches applied to a particular server or device, filter patches based on conditions, or paginate through large sets of patch records.

Properties

Name Meaning
X USER ID The User Id required for authentication or identification in the request header.
Additional Query Parameters Optional parameters to refine the query:
- Condition: Filter condition for the query.
- 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 output of this node operation is JSON data containing the retrieved asset patch information. This typically includes details about each patch such as patch identifiers, descriptions, statuses, dates, and other metadata as provided by the external API. The exact structure depends on the API response but generally represents a list or collection of patch objects.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the external service.
  • The base URL for the API must be configured in the node credentials.
  • The node uses HTTP headers and query parameters to communicate with the API endpoint.

Troubleshooting

  • Missing or invalid X USER ID: Since the X USER ID header is required, omitting it or providing an incorrect value will likely cause authentication or authorization errors. Ensure the correct user ID is supplied.
  • Invalid query parameters: Providing malformed or unsupported values in additional query parameters like condition, skip, limit, or order_by may result in API errors or empty responses. Validate these inputs carefully.
  • API connectivity issues: Network problems or incorrect base URL configuration can prevent successful API calls. Verify network access and credential settings.
  • Empty or unexpected response: If no patches are returned, check the query conditions and ensure that the asset has associated patches.

Links and References

  • Refer to the external API documentation for detailed information on the asset patches endpoint, including supported query parameters and response schema.
  • n8n documentation on how to configure HTTP header and query parameter inputs for custom nodes.

Discussion