Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the "Connect Secure" API to retrieve kernel module information related to assets. Specifically, the "Retrieve Kernel Modules" operation fetches details about kernel modules based on user-defined query parameters such as conditions, pagination, and sorting. This node is useful in scenarios where users need to programmatically access and analyze kernel module data for asset management, security auditing, or compliance monitoring.

Practical examples include:

  • Fetching all kernel modules loaded on a set of devices filtered by specific criteria.
  • Paginating through large datasets of kernel modules to process them in batches.
  • Sorting kernel modules by attributes like name or load time for reporting purposes.

Properties

Name Meaning
X USER ID User Id header value required for authentication or identification in the API request.
Condition Query condition string to filter kernel modules (e.g., status="active").
Skip Number of records to skip for pagination purposes.
Limit Maximum number of records to return.
Order By Field(s) to order the results by (e.g., "name asc", "load_time desc").

Output

The node outputs JSON data representing the retrieved kernel modules. Each item in the output corresponds to a kernel module record matching the query parameters. The structure typically includes fields describing the kernel module's properties such as its name, version, status, and other metadata as provided by the Connect Secure API.

If binary data were involved (not indicated here), it would represent files or attachments related to kernel modules, but this node focuses on JSON data retrieval.

Dependencies

  • Requires an active connection to the Connect Secure API.
  • Needs an API key or token credential configured in n8n for authentication.
  • The node depends on the @devlikeapro/n8n-openapi-node package and the OpenAPI specification (openapi.json) bundled within the node for request construction and execution.

Troubleshooting

  • Missing or invalid X USER ID: The API requires the "X USER ID" header; ensure it is provided and correct to avoid authentication errors.
  • Invalid query conditions: Malformed or unsupported query strings in the "Condition" property may cause the API to reject the request. Validate syntax according to the API documentation.
  • Pagination issues: Setting "Skip" or "Limit" incorrectly might result in empty responses or incomplete data sets.
  • Order By errors: Using unsupported fields or incorrect syntax in "Order By" can lead to API errors.
  • Credential errors: Ensure the API key/token credential is valid and has sufficient permissions.

Links and References

Discussion