Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node is designed to delete an integration rule within a system called "Connect Secure" via its API. It allows users to specify which integration rule to remove by providing the unique identifier of that rule. This operation is useful in scenarios where outdated or incorrect integration rules need to be cleaned up or removed to maintain system integrity and prevent unwanted data flows.

Practical examples include:

  • Automating cleanup of deprecated integration rules as part of a maintenance workflow.
  • Removing integration rules that are no longer valid after changes in business processes.
  • Managing integration configurations programmatically without manual intervention.

Properties

Name Meaning
X USER ID The user identifier header required by the API to authenticate or track the requestor.
Id The numeric identifier of the integration rule to be deleted.

Output

The node outputs JSON data representing the response from the API after attempting to delete the specified integration rule. Typically, this will include confirmation of deletion or error details if the operation failed.

No binary data output is expected from this node.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • Needs network access to the Connect Secure service endpoint.
  • The node depends on the OpenAPI specification defined in openapi.json for request construction.
  • Uses the @devlikeapro/n8n-openapi-node package to build and parse operations based on the OpenAPI spec.

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 Id value: Providing an invalid or non-existent integration rule ID will result in an error from the API. Verify the ID before running the node.
  • Authentication errors: Make sure the API key credential is configured properly in n8n and has sufficient permissions.
  • Network issues: Connectivity problems to the Connect Secure API endpoint can cause failures. Check network settings and endpoint availability.
  • API errors: The API might return errors due to internal issues or invalid requests. Review the returned error message for guidance.

Links and References

Discussion