Meilisearch

Overview

This node allows you to interact with the Meilisearch API, specifically to delete an existing API key. This operation is useful for managing access control in your Meilisearch instance by removing keys that are no longer needed or have been compromised.

Common scenarios:

• Revoking access for users or applications that should no longer interact with your Meilisearch instance.
• Automating key rotation processes as part of security best practices.
• Cleaning up unused or expired API keys.

Practical example:
You might use this node in a workflow that automatically deletes API keys after a certain period or when a user account is deactivated.

Properties

Output

The output will be a JSON object indicating the result of the deletion operation. Typically, for a successful delete operation, the response may be empty or contain a status confirmation. The exact structure depends on the Meilisearch API but generally does not include binary data.

Dependencies

• External Service: Requires access to a running Meilisearch instance.
• API Key: You must provide valid Meilisearch API credentials (configured in n8n as meilisearchApi).
• Environment Variable: The base URL for Meilisearch (host_url) must be set in the credentials.

Troubleshooting

• Invalid UID: If the provided UID does not correspond to an existing API key, the node may return an error such as "Key not found." Double-check the UID value.
• Authentication Error: If the API key used for authentication is invalid or lacks sufficient permissions, you may see errors like "Unauthorized" or "Forbidden." Ensure your credentials are correct and have the necessary rights.
• Connection Issues: Errors like "Could not connect to Meilisearch" indicate network or configuration problems. Verify the host_url and network connectivity.

Links and References

• Meilisearch API Reference – Keys
• n8n Documentation – Credentials
• Meilisearch Security Guide