Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node is designed to delete a suppressed vulnerability record from the "Vulnerabilities" resource in the Connect Secure API. It is useful in scenarios where you want to programmatically remove a previously suppressed vulnerability, for example, when a vulnerability is no longer relevant or was suppressed by mistake.

Practical examples include:

  • Automating cleanup of suppressed vulnerabilities after remediation.
  • Integrating with security workflows to manage vulnerability states dynamically.

Properties

Name Meaning
X USER ID User Id (string) - identifies the user making the request; sent as a header X-USER-ID. This is required.
Id id (number) - the identifier of the suppressed vulnerability to delete. This is required.

Output

The node outputs JSON data representing the response from the API after attempting to delete the suppressed vulnerability. The exact structure depends on the API's response but typically includes confirmation of deletion or error details.

No binary data output is expected from this operation.

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 within n8n.
  • The user must provide the X-USER-ID header value and the id of the suppressed vulnerability to delete.

Troubleshooting

  • Missing or invalid X-USER-ID header: The API may reject requests without a valid user ID header. Ensure this property is set correctly.
  • Invalid or non-existent id: If the specified suppressed vulnerability ID does not exist, the API will likely return an error indicating that the resource was not found.
  • Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
  • Network or connectivity issues: Ensure that the Connect Secure API endpoint is reachable from the n8n instance.

Common error messages might include unauthorized access, resource not found, or bad request due to missing parameters. Resolving these usually involves checking credentials, input values, and network connectivity.

Links and References

  • Connect Secure API documentation (refer to official docs for detailed API endpoints and authentication)
  • n8n documentation on creating and using API key credentials
  • General REST API best practices for handling DELETE operations

Discussion