Actions24
- Documents Actions
- Indexes Actions
- Keys Actions
- Search Actions
- Settings Actions
- Tasks Actions
Overview
This node integrates with the Meilisearch API, specifically focusing on managing documents within a Meilisearch index. It allows users to interact with document data stored in a specified search index, enabling operations such as adding, updating, or deleting documents.
Common scenarios where this node is beneficial include:
- Synchronizing external databases or content management systems with a Meilisearch index.
- Automating document updates in response to changes in source data.
- Managing searchable content dynamically for applications relying on Meilisearch.
For example, a user might use this node to add new product descriptions to a Meilisearch index whenever new products are added to their e-commerce platform, ensuring search results stay up-to-date.
Properties
| Name | Meaning |
|---|---|
| Index UID | The unique identifier (name) of the Meilisearch index where documents will be managed. |
The "Index UID" property is required and must be selected from existing indexes retrieved dynamically from the Meilisearch instance.
Output
The node outputs JSON data representing the result of the document operation performed on the specified index. This typically includes confirmation of success, details about the affected documents, or error information if the operation failed.
If the node supports binary data output (not explicitly shown in the provided code), it would represent any binary content related to documents, such as attachments or media files associated with indexed documents.
Dependencies
- Requires connection to a Meilisearch server, configured via an API host URL and an API key credential.
- The node expects valid credentials for authenticating requests to the Meilisearch API.
- Network access to the Meilisearch instance must be available from the n8n environment.
Troubleshooting
Common issues:
- Invalid or missing API credentials can cause authentication failures.
- Specifying a non-existent or misspelled Index UID will result in errors when attempting to manage documents.
- Network connectivity problems between n8n and the Meilisearch server can prevent successful API calls.
Error messages:
- Authentication errors typically indicate invalid API keys or misconfigured credentials.
- "Index not found" errors suggest the chosen Index UID does not exist; verify the index name.
- Request timeouts or connection errors imply network issues; check server availability and firewall settings.
Resolving these usually involves verifying credentials, confirming index names, and ensuring network connectivity.