Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the Connect Secure API to delete a tag rule. It is useful in scenarios where you need to programmatically remove specific tagging rules from your Connect Secure environment, such as cleaning up outdated or incorrect tags that affect data classification or processing.

For example, if you have automated workflows that manage tags for security policies or data categorization, this node can be used to delete a tag rule by its identifier, ensuring your tagging system stays accurate and up-to-date.

Properties

Name Meaning
X USER ID User Id (string) - required header to identify the user making the request.
Id id (number) - the unique identifier of the tag rule to delete.

Output

The node outputs JSON data representing the response from the Connect Secure API after attempting to delete the specified tag rule. This typically includes confirmation of deletion or error details if the operation failed.

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 the provided user ID having sufficient permissions to delete tag rules.
  • No additional environment variables are explicitly required beyond standard API authentication setup.

Troubleshooting

  • Common issues:

    • Invalid or missing X USER ID header may cause authentication or authorization failures.
    • Providing an invalid or non-existent tag rule id will result in errors indicating the resource was not found.
    • Network connectivity issues to the Connect Secure API endpoint can cause request failures.
  • Error messages:

    • "Unauthorized" or "Forbidden": Check that the API key and user ID are correct and have proper permissions.
    • "Not Found": Verify that the tag rule ID exists before attempting deletion.
    • Timeout or network errors: Ensure the API endpoint is reachable and there are no firewall restrictions.

Links and References

  • Connect Secure API documentation (refer to your organization's API docs for detailed endpoints and authentication)
  • n8n documentation on creating custom nodes and handling HTTP requests

Discussion