Actions24
- Documents Actions
- Indexes Actions
- Keys Actions
- Search Actions
- Settings Actions
- Tasks Actions
Overview
This node integrates with the Meilisearch API to manage documents within a specified index. Specifically, the "Delete Batch of Documents" operation allows users to delete multiple documents at once by providing an array of document IDs. This is useful for bulk removal of outdated or irrelevant data from a search index, helping maintain accurate and efficient search results.
Practical examples include:
- Removing a batch of product entries that are no longer available in an e-commerce catalog.
- Deleting multiple user-generated content items flagged as inappropriate.
- Clearing out old log entries or records from a searchable database.
Properties
| Name | Meaning |
|---|---|
| Index UID | The unique identifier (name) of the index from which documents will be deleted. |
| UIDs | A JSON array string containing the document IDs to delete in batch from the specified index. |
Output
The node outputs JSON data representing the response from the Meilisearch API after attempting to delete the batch of documents. This typically includes information about the task status or confirmation of deletion. There is no binary output associated with this operation.
Dependencies
- Requires connection to a Meilisearch instance via its REST API.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The base URL of the Meilisearch server must be provided in the node's credential configuration.
Troubleshooting
- Invalid Index UID: If the specified index does not exist, the API will return an error. Verify the index name is correct and exists on the Meilisearch server.
- Malformed UIDs JSON: The UIDs property expects a valid JSON array string. Errors occur if the format is incorrect. Ensure the input is a properly formatted JSON array of strings or numbers.
- Authentication Errors: Missing or invalid API credentials will cause authorization failures. Confirm that the API key/token is correctly set up in n8n.
- Network Issues: Connection problems to the Meilisearch server can cause request failures. Check network connectivity and server availability.