Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation allows users to create a "suppress vulnerability" entry in the Vulnerabilities resource of the Connect Secure API. It is useful for scenarios where certain vulnerabilities need to be marked as suppressed or ignored, possibly because they are false positives or have been otherwise addressed outside the system. For example, a security team might use this node to programmatically suppress known benign vulnerabilities during automated scans.

Properties

Name Meaning
X USER ID The user identifier making the request. This is required and sent as an HTTP header.
Data JSON object containing the data for the suppression entry. By default, it includes an internal_users field which is an array (empty by default). This property is sent as the request body.

Output

The node outputs the JSON response from the API after creating the suppress vulnerability entry. The exact structure depends on the API's response but typically includes confirmation details about the created suppression record. 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 uses the Connect Secure API endpoint defined in its OpenAPI specification.
  • No additional environment variables are explicitly required beyond the API authentication.

Troubleshooting

  • Missing or invalid X USER ID header: The API requires the X USER ID header; ensure it is provided and correctly formatted.
  • Invalid JSON in Data property: The Data input must be valid JSON. Errors parsing this will cause the request to fail.
  • Authentication errors: Ensure the API key credential is correctly configured and has sufficient permissions.
  • API connectivity issues: Network problems or incorrect API endpoint configuration can cause failures.
  • Check the API response message for specific error codes and messages to guide resolution.

Links and References

  • Connect Secure API documentation (refer to your organization's API docs for detailed schema and examples)
  • n8n documentation on using HTTP headers and JSON body parameters in nodes

Discussion