AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node operation deletes a specific credential identified by its ID. It is useful in scenarios where you need to programmatically remove stored credentials from a system, for example, when a user revokes access or when cleaning up unused credentials to maintain security hygiene.

Practical examples include:

  • Automatically deleting API keys or tokens that are no longer valid.
  • Removing user credentials as part of an account deletion workflow.
  • Managing credential lifecycle in automated DevOps pipelines.

Properties

Name Meaning
X USER ID User Id - a required string header used to identify the user making the delete request.
Id The numeric identifier of the credential to be deleted.

Output

The output JSON typically contains the response from the delete operation, which may include confirmation of deletion or status information. No binary data output is expected.

Dependencies

  • Requires an API key credential for authentication with the external service.
  • The base URL and other request defaults are configured via node credentials.
  • The node depends on an external API endpoint to perform the delete operation.

Troubleshooting

  • Missing or invalid X USER ID: The node requires a valid user ID header; ensure it is provided and correct.
  • Invalid credential ID: If the specified credential ID does not exist, the API may return an error indicating the resource was not found.
  • Authentication errors: Ensure the API key credential is correctly configured and has permissions to delete credentials.
  • Network issues: Verify connectivity to the external API endpoint.

Common error messages might include unauthorized access, resource not found, or bad request due to missing parameters. Resolving these involves checking input values, credentials, and network settings.

Links and References

  • Refer to the external API documentation for credential management and deletion endpoints.
  • n8n documentation on managing credentials and using HTTP request nodes for API interactions.

Discussion