Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node is designed to delete a backup software entry by its identifier. It is useful in scenarios where you need to programmatically remove backup software records from a system, for example, when cleaning up outdated or unused backup configurations. A practical use case would be automating the removal of backup software entries as part of a maintenance workflow.

Properties

Name Meaning
X USER ID User Id (string) - The identifier of the user making the request, sent as a header named X-USER-ID. This is required.
Id id (number) - The unique identifier of the backup software entry to delete. This is required.

Output

The node outputs JSON data representing the result of the delete operation. Typically, this will include confirmation of deletion or any relevant status information returned by the API. There is no indication that binary data is output by this node.

Dependencies

  • Requires an API key credential for authentication with the Connect Secure API.
  • Depends on the Connect Secure API endpoint that manages backup software entries.
  • The node uses HTTP headers to pass the user ID (X-USER-ID).
  • Requires proper configuration of the API credentials within n8n.

Troubleshooting

  • Missing or invalid X USER ID header: Ensure the user ID is provided and correctly mapped to the header; otherwise, the API may reject the request.
  • Invalid or non-existent Id: If the specified backup software ID does not exist, the API might return an error indicating the resource was not found.
  • Authentication errors: Verify that the API key credential is valid and has sufficient permissions to delete backup software entries.
  • Network or API errors: Check connectivity and API availability if requests fail unexpectedly.

Links and References

  • Refer to the Connect Secure API documentation for details on the backup software deletion endpoint.
  • Consult n8n documentation on how to configure API credentials and HTTP headers in custom nodes.

Discussion