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 interacts with Algolia's multi-cluster management API to retrieve information about a specific user ID within the cluster mapping. The "Get user id" operation fetches data related to a user ID stored in the cluster mapping, which can be useful for monitoring or managing user assignments across clusters in a multi-cluster setup.
Typical use cases include:
- Retrieving detailed information about a particular user ID's cluster assignment.
- Auditing or troubleshooting user distribution in a multi-cluster environment.
- Integrating cluster user data into workflows for reporting or further processing.
For example, you might use this node to get the cluster details of a user "user1" to verify their assigned cluster or to check metadata associated with that user ID.
Properties
| Name | Meaning |
|---|---|
| User ID | Unique identifier of the user who makes the search request. Must match pattern ^[a-zA-Z0-9 \-*.]+$. |
Output
The node outputs JSON data representing the user ID information retrieved from the cluster mapping. This typically includes details about the user's cluster assignment and any associated metadata as returned by the Algolia API endpoint /1/clusters/mapping/{userID}.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential with appropriate permissions to access Algolia's cluster mapping endpoints.
- The node uses the Algolia API base URL constructed from the provided application ID credential.
- Network connectivity to Algolia's API service is necessary.
Troubleshooting
- Invalid User ID Format: If the User ID does not conform to the allowed pattern (
^[a-zA-Z0-9 \-*.]+$), the request may fail. Ensure the User ID input matches the required format. - Permission Errors: Insufficient API key permissions will result in authorization errors. Verify that the API key used has rights to access cluster mapping data.
- User ID Not Found: If the specified User ID does not exist in the cluster mapping, the API may return a 404 or empty response. Confirm the User ID is correct and exists.
- Network Issues: Connectivity problems to Algolia's API will cause request failures. Check network settings and firewall rules.
- API Rate Limits: Excessive requests may hit Algolia's rate limits, causing errors. Implement retry logic or reduce request frequency if needed.