Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation, Retrieve Asset Patches Info, is designed to fetch information about patches related to assets from the Connect Secure API. It allows users to query asset patch data with flexible filtering, pagination, and sorting options. This can be particularly useful in scenarios where you need to monitor or audit patch statuses on various assets within an IT environment, track compliance, or generate reports on patch deployments.

Practical examples include:

  • Retrieving all patches applied to a specific set of assets filtered by certain conditions.
  • Paginating through large sets of patch records to process them in batches.
  • Sorting patch information by date or severity to prioritize remediation efforts.

Properties

Name Meaning
X USER ID User identifier required for authentication or tracking purposes in the API request header.
Condition Query condition string to filter the asset patches info based on specified criteria.
Skip Number of records to skip, used for pagination to offset the starting point of results.
Limit Maximum number of records to return, controlling the size of the result set.
Order By Field(s) by which to order the returned patch records, e.g., by date or priority.

Output

The node outputs JSON data containing the retrieved asset patch information. The structure typically includes details about each patch such as patch identifiers, status, associated asset information, timestamps, and other metadata as provided by the Connect Secure API.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Connect Secure API.
  • The node depends on the Connect Secure API being accessible and properly configured.
  • No additional external services are explicitly required beyond the API access.

Troubleshooting

  • Missing or invalid X USER ID: Since the X USER ID header is mandatory, omitting it or providing an incorrect value will likely cause authentication or authorization errors. Ensure the user ID is correct and included.
  • Invalid query conditions: Malformed or unsupported query strings in the Condition property may lead to API errors or empty results. Validate the syntax and semantics of the query condition.
  • Pagination issues: Setting Skip or Limit incorrectly (e.g., negative numbers) might cause unexpected behavior or errors. Use non-negative integers.
  • Ordering errors: Providing invalid fields in Order By could result in API errors or default ordering. Confirm that the field names match those supported by the API.
  • API connectivity problems: Network issues or incorrect API credentials will prevent successful data retrieval. Verify network access and credential validity.

Links and References


Note: The above summary is based solely on static analysis of the provided source code and property definitions.

Discussion