Actions52
- Advanced Actions
- Api Keys Actions
- Clusters Actions
- Dictionaries Actions
- Indices Actions
- Records Actions
- Rules Actions
- Search Actions
- Synonyms Actions
- Vaults Actions
Overview
This node operation lists user IDs assigned to a multi-cluster Algolia application. It retrieves the user IDs mapped across different clusters, which can be useful for managing and monitoring user distribution in a multi-cluster setup. Since the data is aggregated from multiple clusters, the response may not be real-time and could take a few seconds to fetch.
Common scenarios:
- Auditing or reporting on user IDs distributed across clusters.
- Monitoring cluster usage by user ID.
- Integrating with workflows that require knowledge of user assignments in a multi-cluster environment.
Example use case:
You want to generate a report of all user IDs currently assigned to your multi-cluster Algolia setup to analyze load distribution or prepare for cluster maintenance.
Properties
| Name | Meaning |
|---|---|
| Page | Choose between "Integer" or "Null" to specify pagination mode for listing user IDs. |
| Page (number) | If "Page" is set to "Integer", this specifies the page number (minimum 0). |
| Page (null) | If "Page" is set to "Null", this disables pagination by sending a null value. |
| Hits Per Page | Number of user IDs to retrieve per page (default is 100). |
Output
The node outputs JSON data containing the list of user IDs assigned to the clusters. The structure corresponds to the API response from the Algolia clusters mapping endpoint. The output includes user ID details as returned by the Algolia API.
No binary data is output by this operation.
Dependencies
- Requires an API key credential with appropriate permissions to access the Algolia clusters mapping API.
- The node uses the Algolia API base URL constructed from the provided application ID credential.
- No additional external dependencies are required.
Troubleshooting
- Delayed or stale data: Because the user ID mapping is aggregated from multiple clusters, the response might not reflect real-time changes immediately. Allow some time for updates to propagate.
- Invalid API credentials: Ensure the API key used has sufficient permissions to access cluster mappings.
- Pagination errors: When specifying the page number, ensure it is a non-negative integer. Using invalid values may cause API errors.
- Network issues: Verify network connectivity to the Algolia API endpoint.
Links and References
- Algolia Multi-Cluster User ID Mapping API
- Algolia API Keys and Permissions
- n8n Documentation on Credentials
If you need further details about other operations or resources, feel free to ask!