Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the Connect Secure API to retrieve Windows Protection Status data related to assets. It is designed to query asset protection information, which can be useful for IT administrators or security teams monitoring endpoint protection status across an organization’s Windows devices.

Typical use cases include:

  • Fetching the current protection status of Windows machines in an enterprise.
  • Filtering and sorting asset protection data based on specific conditions.
  • Paginating through large datasets of asset protection records.

For example, a user might want to retrieve all Windows assets that have outdated antivirus definitions or are missing certain protection features, using query conditions and ordering options.

Properties

Name Meaning
X USER ID User identifier required for authentication or tracking purposes; sent as a request header X-USER-ID.
Condition Query condition string to filter the results based on specific criteria (e.g., status filters).
Skip Number of records to skip, used for pagination.
Limit Maximum number of records to return.
Order By Field(s) by which to order the returned results.

Output

The node outputs JSON data representing the Windows Protection Status records retrieved from the Connect Secure API. Each item in the output corresponds to one asset's protection status details.

If binary data were involved (not indicated here), it would typically represent files or attachments related to the asset data, but this node focuses on JSON responses.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • The node depends on the external Connect Secure service being accessible.
  • No additional environment variables are explicitly required beyond the API credential.

Troubleshooting

  • Authentication errors: Ensure the API key credential is correctly configured and has sufficient permissions.
  • Empty results: Verify the query condition syntax and values; incorrect filters may yield no data.
  • Pagination issues: If too many records are requested without proper skip/limit settings, the API might reject the request or timeout.
  • Invalid order_by fields: Using unsupported fields in the "Order By" property may cause errors or unexpected sorting.

Links and References

  • Connect Secure API documentation (refer to your organization's internal API docs or vendor-provided resources).
  • n8n documentation on creating and using HTTP Request nodes and custom credentials.

Discussion