h2oGPTe icon

h2oGPTe

h2oGPTe is an AI-powered search assistant for your internal teams to answer questions gleaned from large volumes of documents, websites and workplace content.

Actions198

Overview

The "Deletes Collection" operation under the "Chat" resource allows users to delete a specific chat session by its unique session ID. This node is useful in scenarios where you want to programmatically remove chat sessions, for example, to clean up old or irrelevant conversations, manage storage, or enforce data retention policies.

Practical examples include:

  • Automatically deleting chat sessions after a certain period.
  • Removing test or temporary chat sessions created during development or testing.
  • Managing user requests to delete their chat history.

Properties

Name Meaning
Session ID The unique identifier of the chat session to be deleted.
Additional Options Optional settings; currently supports:
- Timeout Timeout duration in seconds for the delete request (default is 300 seconds).

Output

The output of this operation typically contains the response from the API indicating the success or failure of the deletion request. The json output field will hold the full HTTP response returned by the server, which may include status codes and messages confirming the deletion.

This node does not output binary data.

Dependencies

  • Requires an API key credential for authentication with the external service.
  • The base URL for API requests is configured via credentials.
  • The node sends an HTTP DELETE request to the endpoint /chats/{session_id}.

Troubleshooting

  • Common Issues:

    • Invalid or missing Session ID: The node requires a valid session ID to delete the chat session.
    • Authentication errors: Ensure that the API key credential is correctly configured and has permissions to delete chat sessions.
    • Timeout errors: If the deletion takes longer than the specified timeout, the request may fail. Adjust the timeout value if necessary.
  • Error Messages:

    • 404 Not Found: The specified chat session ID does not exist.
    • 401 Unauthorized or 403 Forbidden: Authentication failed or insufficient permissions.
    • 408 Request Timeout: The request timed out; consider increasing the timeout setting.

Links and References

  • Refer to the API documentation of the chat service for details on the DELETE /chats/{session_id} endpoint.
  • Consult n8n documentation on configuring API key credentials and HTTP request nodes for further setup guidance.

Discussion