Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the "Vulnerabilities" resource of the Connect Secure API to retrieve records based on specified query parameters. It is useful for scenarios where users need to fetch vulnerability data filtered by conditions, paginated, and ordered according to their needs. For example, a security analyst could use this node to pull recent vulnerability records that match certain criteria, skip a number of entries, limit the results returned, and order them by severity or date.

Properties

Name Meaning
X USER ID User Id required for authentication, passed as a header in the API request.
Condition Query condition string to filter the vulnerabilities records (e.g., status="open").
Skip Number of records to skip, used for pagination.
Limit Maximum number of records to return.
Order By Field(s) to order the results by (e.g., "date desc", "severity asc").

Output

The node outputs JSON data containing the retrieved vulnerability records matching the query parameters. The structure corresponds directly to the API response for vulnerabilities and typically includes fields such as vulnerability identifiers, descriptions, statuses, dates, and other relevant metadata. There is no indication that binary data is output by this node.

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 indicated beyond the bundled OpenAPI client and lodash library.

Troubleshooting

  • Missing or invalid X USER ID: Since the 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 against the API documentation.
  • Pagination issues: Setting "Skip" or "Limit" incorrectly (e.g., negative numbers) might cause unexpected results or errors.
  • Ordering errors: Using invalid field names or formats in "Order By" can lead to API rejections.
  • API connectivity: Network issues or incorrect API credentials will prevent successful data retrieval.

Links and References

  • Connect Secure API Documentation (refer to official docs for query syntax and available fields)
  • n8n Documentation on HTTP Request Nodes and Custom Node Development

Discussion