Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node allows users to delete an Event Set by specifying its unique identifier. It is useful in scenarios where you need to programmatically remove event sets from a system, such as cleaning up outdated or incorrect data, managing event lifecycle, or automating administrative tasks related to event management.

For example, if you have a list of event sets and want to delete one based on its ID, this node can be used to perform that deletion via an API call, ensuring the event set is removed without manual intervention.

Properties

Name Meaning
X USER ID User Id (string) - identifies the user making the request; sent as a header X-USER-ID
Id id (number) - the unique identifier of the Event Set to delete

Output

The node outputs JSON data representing the response from the deletion operation. Typically, this will include confirmation of successful deletion or error details if the operation failed.

No binary data output is expected from this node.

Dependencies

  • Requires an API key credential for authentication with the Connect Secure API.
  • The node depends on the Connect Secure API being accessible and properly configured.
  • The X-USER-ID header must be provided to identify the user performing the deletion.

Troubleshooting

  • Missing or invalid X USER ID header: The API may reject requests without a valid user ID header. Ensure this property is correctly set.
  • Invalid or non-existent Event Set ID: If the specified ID does not exist, the API might return an error indicating the resource was not found.
  • Authentication errors: Make sure the API key credential is valid and has sufficient permissions to delete event sets.
  • Network or connectivity issues: Verify that the API endpoint is reachable from your n8n instance.

Links and References

  • Refer to the Connect Secure API documentation for detailed information about the Event Set deletion endpoint and required headers.
  • Consult n8n documentation on how to configure API credentials and use HTTP headers in nodes.

Discussion