Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the Connect Secure API to retrieve asset security report data. It is designed to query and fetch detailed security reports related to assets, which can be useful for security analysts, IT administrators, or compliance teams who need to monitor and analyze asset security status programmatically.

Typical use cases include:

  • Automating the retrieval of security reports for assets in an enterprise environment.
  • Integrating asset security data into dashboards or alerting systems.
  • Filtering and sorting asset security information based on specific conditions or criteria.

For example, a user might configure this node to fetch the latest security reports for all assets that meet certain risk conditions, limit the number of records returned, and order them by severity or date.

Properties

Name Meaning
X USER ID User Id required for authentication; passed as a header named X-USER-ID
Condition Query condition to filter the asset security reports (e.g., filter expressions)
Skip Number of records to skip in the result set (for pagination)
Limit Maximum number of records to return
Order By Field(s) to order the results by (e.g., date, severity)

Output

The node outputs JSON data containing the retrieved asset security report records matching the specified query parameters. The structure of each record corresponds to the asset security report schema provided by the Connect Secure API.

No binary data output is indicated by the source code or properties.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • The node depends on the Connect Secure API being accessible and properly configured.
  • No additional external dependencies are explicitly mentioned beyond the bundled OpenAPI client.

Troubleshooting

  • Authentication errors: Ensure the API key or user ID is correctly set and has sufficient permissions.
  • Empty results: Verify the query condition syntax and values; incorrect filters may yield no data.
  • Pagination issues: If using skip and limit, ensure values are within valid ranges and consistent with the API limits.
  • Ordering problems: Confirm the order_by field matches valid sortable fields supported by the API.

Common error messages would likely relate to invalid credentials, malformed queries, or exceeding rate limits. Checking API documentation and logs will help resolve these.

Links and References

Discussion