Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node enables users to delete a specific Application Baseline Rule by its identifier. It is useful in scenarios where an existing baseline rule needs to be removed from the system, such as when a rule is obsolete, incorrect, or no longer applicable. For example, security administrators can automate the cleanup of outdated application baseline rules to maintain an accurate and efficient security posture.

Properties

Name Meaning
X USER ID The user identifier required for authentication or tracking purposes in the API request.
Id The numeric identifier of the Application Baseline Rule that should be deleted.

Output

The node outputs JSON data representing the response from the deletion operation. Typically, this will include confirmation of successful deletion or details about any errors encountered. There is no indication that the node outputs binary data.

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 environment variables are explicitly required beyond the API credential.

Troubleshooting

  • Missing or invalid X USER ID: If the user ID header is not provided or incorrect, the API may reject the request. Ensure the "X USER ID" property is set correctly.
  • Invalid or non-existent Id: Providing an invalid or non-existent rule ID will likely result in an error response indicating the resource was not found.
  • API authentication failure: Ensure the API key credential is valid and has sufficient permissions to delete application baseline rules.
  • Network issues: Connectivity problems to the Connect Secure API endpoint can cause failures; verify network access and endpoint URL correctness.

Links and References

  • Refer to the Connect Secure API documentation for detailed information on deleting application baseline rules.
  • Consult n8n documentation on how to configure API credentials and use HTTP headers in requests.

Discussion