Actions52
- Advanced Actions
- Api Keys Actions
- Clusters Actions
- Dictionaries Actions
- Indices Actions
- Records Actions
- Rules Actions
- Search Actions
- Synonyms Actions
- Vaults Actions
Overview
The "Get objects" operation of the "Records" resource in this Algolia node allows users to retrieve one or more records from one or multiple indices by specifying their object IDs. This operation is useful when you need to fetch specific records directly without performing a search query, for example, to display detailed information about selected items or to synchronize data.
Typical use cases include:
- Fetching multiple product details by their unique IDs from different indices.
- Retrieving user profiles or documents stored in various indices.
- Batch retrieval of records for data processing or export.
Properties
| Name | Meaning |
|---|---|
| Get Objects Params | Request parameters; currently supports only "Requests". |
| Requests | A collection of individual requests, each specifying: |
| - Attributes To Retrieve | List of attributes to return for the record. If empty or not specified, all retrievable attributes are returned. |
| - Object ID | The unique identifier of the record to retrieve. |
| - Index Name | The name of the index from which to retrieve the record. |
The "Requests" property accepts multiple entries, allowing batch retrieval of records from different indices with optional attribute filtering.
Output
The output contains the JSON response from the Algolia API corresponding to the requested records. Each item in the output corresponds to a record retrieved, preserving the order of the requests.
The json field includes the full record data as returned by Algolia, including all requested attributes or all retrievable attributes if none were specified.
No binary data output is indicated for this operation.
Dependencies
- Requires an Algolia application ID and an API key credential configured in n8n.
- The node sends HTTP POST requests to the Algolia API endpoint
/1/indexes/*/objects. - Proper permissions on the API key are necessary to perform read operations on the specified indices.
Troubleshooting
- Empty results: Ensure that the object IDs and index names are correct and that the records exist.
- Permission errors: Verify that the API key used has sufficient rights to access the specified indices.
- Malformed attributesToRetrieve: The attributes list must be a valid JSON array; invalid JSON will cause request failures.
- Rate limits: Large batch requests may hit Algolia's indexing or query rate limits; consider splitting requests if errors occur.
Links and References
This summary describes the static configuration and expected behavior of the "Get objects" operation for the "Records" resource in the Algolia n8n node based on the provided source code and parameter definitions.