Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node allows users to delete an Asset by specifying its unique identifier. It is useful in scenarios where you need to programmatically remove assets from a system, such as cleaning up unused or obsolete resources, managing asset lifecycle, or automating administrative tasks related to asset management.

For example, if you have a list of asset IDs that are no longer needed, this node can be used within an automation workflow to delete each asset automatically without manual intervention.

Properties

Name Meaning
X USER ID The user identifier required for authentication or authorization purposes.
Id The unique numeric identifier of the asset to be deleted.

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 authenticating with the Connect Secure API.
  • Needs proper configuration of the API credentials within n8n to authorize requests.
  • Depends on the external Connect Secure API service to perform the delete operation.

Troubleshooting

  • Missing or invalid "X USER ID" header: Ensure that the user ID is correctly provided and valid; otherwise, the API may reject the request.
  • Invalid asset Id: Providing an incorrect or non-existent asset ID will likely cause the API to return an error indicating the asset was not found.
  • Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions to delete assets.
  • Network or API downtime: Temporary connectivity issues or API service outages can cause failures; retrying later or checking service status may help.

Links and References

  • Refer to the Connect Secure API documentation for detailed information about the asset deletion endpoint and required headers.
  • Consult n8n documentation on how to configure API credentials and use HTTP request nodes for custom API interactions.

Discussion