Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the "Asset" resource of an API to retrieve information about open ports on assets. It is useful in scenarios where you need to audit, monitor, or analyze network assets by fetching details about which ports are currently open. For example, a security analyst might use this node to gather data on open ports across multiple assets to identify potential vulnerabilities or unauthorized services.

Properties

Name Meaning
X USER ID User identifier required for authentication or tracking purposes in the API request headers.
Condition Query condition to filter the assets based on specific criteria (e.g., status, type).
Skip Number of records to skip, useful for pagination.
Limit Maximum number of records to return, controlling the size of the response.
Order By Field(s) by which to order the results, e.g., by port number or asset name.

Output

The node outputs JSON data containing details about the open ports of assets retrieved from the API. The structure typically includes fields describing each open port and associated asset metadata. There is no indication that binary data is returned by this operation.

Dependencies

  • Requires an API key or token credential to authenticate requests to the Connect Secure API.
  • The node depends on the external Connect Secure API service being available.
  • Proper configuration of the API credentials within n8n is necessary.

Troubleshooting

  • Common issues:
    • Missing or invalid user ID header (X USER ID) may cause authentication failures.
    • Incorrect query conditions can result in empty responses or errors.
    • Pagination parameters (skip and limit) set improperly might lead to incomplete data retrieval.
  • Error messages:
    • Authentication errors usually indicate missing or incorrect API credentials or user ID.
    • Validation errors may occur if query parameters are malformed.
  • Resolutions:
    • Ensure the "X USER ID" property is correctly set.
    • Verify query syntax and parameter values.
    • Check API credentials and connectivity.

Links and References

  • Refer to the official Connect Secure API documentation for detailed information on the "Asset" resource and its open ports endpoint.
  • Consult n8n documentation on how to configure API credentials and use HTTP request nodes for similar integrations.

Discussion