Actions22
- Broadcasts Actions
- Embeddings Actions
- Contacts Actions
- Conversations Actions
- Tags Actions
Overview
The node operation "Deleteachunkbyid" under the "Embeddings" resource is designed to delete a specific chunk of data identified by its unique Chunk Id. This operation is useful in scenarios where you need to manage or clean up stored embedding chunks, for example, removing outdated or irrelevant pieces of data from an embeddings database or service.
Practical examples include:
- Removing a chunk of text embedding that is no longer relevant after content updates.
- Cleaning up embedding storage to maintain performance and reduce storage costs.
- Managing embedding lifecycle by deleting specific chunks based on user actions or automated workflows.
Properties
| Name | Meaning |
|---|---|
| Chunk Id | The unique identifier of the chunk to be deleted. This is a required string input. |
Output
The output of this operation typically contains a JSON object indicating the result of the deletion request. It may include confirmation of successful deletion or details about any errors encountered.
If the node supports binary data output, it would generally represent any files or raw data returned by the API, but based on the provided code snippet and operation, the primary output is JSON confirming the deletion status.
Dependencies
- Requires an API key credential to authenticate requests to the external service managing embeddings.
- The node depends on a base URL configured in the credentials to direct API calls.
- Uses HTTP headers specifying JSON content type for communication with the API.
Troubleshooting
- Missing or invalid Chunk Id: Ensure the Chunk Id property is provided and correctly formatted; otherwise, the API will reject the request.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions to delete embedding chunks.
- Network or API endpoint issues: Confirm that the base URL is correct and the external service is reachable.
- Error responses from API: Check the JSON output for error messages returned by the API, which can indicate reasons such as non-existent chunk IDs or insufficient permissions.
Links and References
- Refer to the external embedding service API documentation for detailed information on chunk management and deletion endpoints.
- n8n documentation on creating and using credentials for API authentication.
- General REST API best practices for handling delete operations.