Actions52
- Advanced Actions
- Api Keys Actions
- Clusters Actions
- Dictionaries Actions
- Indices Actions
- Records Actions
- Rules Actions
- Search Actions
- Synonyms Actions
- Vaults Actions
Overview
The "Records - Multiple batch" operation in this Algolia node allows users to add, update, or delete multiple records across multiple indices in a single API request. This batch processing capability is useful for efficiently managing large datasets by reducing the number of individual API calls and improving data integrity during bulk operations.
Typical use cases include:
- Synchronizing multiple indices with new or updated data.
- Deleting or updating many records at once across different indices.
- Performing complex multi-index updates in a single transaction to maintain consistency.
For example, an e-commerce platform might update product information across several regional indices simultaneously or remove outdated records from multiple indices in one batch call.
Properties
| Name | Meaning |
|---|---|
| Batch Params | Selects batch parameters to send; currently supports "Requests" which is a collection of individual record operations. |
| Requests | JSON array representing the list of requests (add, update, delete) to perform on multiple indices. Each request specifies the index and the action details. |
The Batch Params property is a multi-select option but currently only includes "Requests". The Requests property expects a JSON input detailing the batch operations.
Output
The node outputs the response from the Algolia API after performing the multiple batch operations. The output is a JSON object containing the status and results of each batch request. It does not produce binary data.
Dependencies
- Requires an Algolia API key credential configured in n8n for authentication.
- Needs the Algolia Application ID to construct the base URL for API requests.
- The node uses Algolia's REST API endpoint
/1/indexes/*/batchfor multiple batch operations.
Troubleshooting
- Rate Limits: Algolia enforces indexing rate limits. If you exceed these, the API may return errors or throttle requests. To resolve, reduce batch size or space out requests.
- Invalid Requests: Malformed JSON in the
Requestsproperty can cause API errors. Ensure the JSON structure matches Algolia's batch request format. - Authentication Errors: Missing or incorrect API credentials will result in authentication failures. Verify that the API key and App ID are correctly set.
- Index Not Found: Specifying non-existent indices in batch requests may cause errors. Confirm indices exist or handle creation accordingly.
- Partial Failures: Some batch actions may succeed while others fail. Check the response for detailed error messages per request.
Links and References
This summary is based on static analysis of the provided node configuration and bundled source code metadata.