Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation, Retrieve Asset Windows Compatibility under the Company resource, is designed to query and retrieve information about Windows compatibility for assets managed within a system. It allows users to specify filtering conditions, pagination controls, and sorting preferences to tailor the data retrieval according to their needs.

Typical use cases include:

  • Fetching a list of company assets filtered by specific criteria related to Windows compatibility.
  • Paginating through large datasets of asset compatibility records.
  • Sorting the results based on certain fields to prioritize or organize the output.

For example, a user might want to retrieve all assets compatible with a particular Windows version, skip the first 10 records, limit the output to 50 entries, and order them by asset name.

Properties

Name Meaning
X USER ID User Id header required for authentication or identification in the API request.
Condition Query condition string to filter the assets based on specified criteria.
Skip Number of records to skip (for pagination).
Limit Maximum number of records to return (for pagination).
Order By Field(s) by which to order the returned records.

Output

The node outputs JSON data representing the retrieved asset Windows compatibility records. Each item in the output corresponds to an asset entry matching the query parameters. The structure typically includes fields describing the asset and its compatibility details.

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 endpoint that supports querying asset Windows compatibility.
  • Proper configuration of the API credentials in n8n is necessary for successful execution.

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 errors. Ensure the correct user ID is provided.
  • Invalid query conditions: Malformed or unsupported query strings in the Condition property may result in API errors or empty responses. Validate the query syntax according to the API documentation.
  • Pagination issues: Setting Skip or Limit to inappropriate values (e.g., negative numbers) could lead to unexpected results or errors.
  • Ordering errors: Using invalid field names in Order By may cause the API to reject the request or ignore the ordering parameter.

Links and References

Discussion