Actions3
- Index Actions
- Objects Actions
Overview
The List Indices operation of the Index resource in this custom n8n node for Algolia allows users to retrieve a list of all indices available in their Algolia account. This is useful for scenarios where you need to dynamically select or manage indices, audit your search infrastructure, or automate index-related workflows.
Practical examples:
- Automatically listing all indices before performing batch operations.
- Displaying available indices in a dashboard or report.
- Validating the existence of an index before creating or deleting objects.
Properties
| Name | Type | Meaning |
|---|---|---|
| Simplify | Boolean | Whether to return a simplified version of the response instead of the raw data. If enabled, only the essential information (the items array) will be returned, making it easier to use in subsequent workflow steps. |
Output
- The output is provided in the
jsonfield of each item. - If Simplify is enabled, the output will be an array of index objects under the
itemsproperty, each representing an Algolia index with its details (such as name, creation date, etc.). - If Simplify is disabled, the full raw response from the Algolia API is returned, which may include additional metadata.
Example output when "Simplify" is enabled:
[
{
"json": [
{
"name": "products",
"createdAt": "2023-01-01T00:00:00Z",
"updatedAt": "2023-06-01T12:34:56Z",
// ...other index properties
},
{
"name": "users",
"createdAt": "2022-05-10T08:15:30Z",
"updatedAt": "2023-05-20T09:45:00Z"
}
]
}
]
Dependencies
- External Service: Requires access to the Algolia API.
- API Credentials: You must provide valid Algolia credentials (
appIdand API key) configured in n8n. - n8n Configuration: The node expects Algolia credentials to be set up in the n8n credential store as
algoliaApi.
Troubleshooting
Common Issues:
- Invalid Credentials: If the provided Algolia credentials are incorrect or missing, the node will fail to connect to the Algolia API.
- Network Errors: Connectivity issues between n8n and Algolia can cause request failures.
- Permission Denied: The API key used may not have sufficient permissions to list indices.
Error Messages & Resolutions:
"Invalid Application-ID or API key": Check that your Algolia credentials are correct and have the necessary permissions."Request failed with status code 403": Ensure your API key has the right access level for listing indices."ENOTFOUND"or network errors: Verify network connectivity and that the Algolia service is reachable from your n8n instance.