Ragdoll AI icon

Ragdoll AI

Consume Ragdoll AI API

Actions14

Overview

This node integrates with the Ragdoll AI API to manage documents within a knowledge base system. Specifically, the Delete Document operation allows users to remove a document by its unique identifier. This is useful in scenarios where outdated or incorrect documents need to be removed from the knowledge base to maintain data accuracy and relevance.

Practical examples include:

  • Automatically deleting documents that are no longer valid after an update.
  • Cleaning up test or temporary documents created during workflows.
  • Managing document lifecycle by removing obsolete content.

Properties

Name Meaning
Document ID The unique identifier of the document to delete. This is required to specify which document should be removed from the system.

Output

The node outputs the response from the Ragdoll AI API after attempting to delete the specified document. The output is structured as JSON data representing the result of the deletion request. Typically, this may include confirmation of deletion or error details if the operation failed.

The node does not output binary data for this operation.

Dependencies

  • Requires an active connection to the Ragdoll AI API.
  • Needs an API authentication token credential configured in n8n to authorize requests.
  • The base URL for the API is taken from the credential configuration.
  • The node sends HTTP DELETE requests to the endpoint /v1/documents/{documentId}.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent Document ID will likely result in an error response indicating the document was not found.
    • Missing or incorrect API credentials will cause authentication failures.
    • Network connectivity problems can prevent the node from reaching the API.
  • Error messages:

    • 404 Not Found: The specified document ID does not exist. Verify the ID is correct.
    • 401 Unauthorized: Authentication failed. Check that the API key or token is correctly set up.
    • 400 Bad Request: The request parameters might be malformed. Ensure the Document ID is provided and valid.

Resolving these typically involves verifying input parameters, checking credential setup, and ensuring network access to the API endpoint.

Links and References

Discussion