Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation deletes an integration credential from the Connect Secure system. It is useful when you need to revoke or remove access credentials associated with a specific integration, for example, when a credential is no longer valid or should be rotated for security reasons.

Practical scenarios include:

  • Cleaning up unused or expired integration credentials.
  • Automating credential lifecycle management by removing old credentials programmatically.
  • Ensuring compliance by deleting credentials that are no longer authorized.

Properties

Name Meaning
X USER ID The user identifier header required by the API to authenticate or identify the requester.
Id The numeric identifier of the integration credential to delete.

Output

The node outputs JSON data representing the result of the deletion operation. Typically, this will confirm whether the deletion was successful or provide error details if it 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 properly configured in n8n.
  • The X USER ID header must be provided as part of the request headers for authorization or identification purposes.

Troubleshooting

  • Missing or invalid X USER ID header: The API may reject requests without this header or with incorrect values. Ensure the correct user ID is supplied.
  • Invalid or non-existent Id: If the specified integration credential ID does not exist, the API will likely 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 integration credentials.
  • Network or connectivity issues: Confirm that the Connect Secure API endpoint is reachable from the n8n environment.

Links and References

  • Refer to the Connect Secure API documentation for detailed information about the integration credential deletion endpoint and required headers.
  • Consult n8n documentation on how to configure API key credentials and use HTTP headers in node parameters.

Discussion