Overview
This node retrieves user-specific values from the Recombee recommendation service. It is designed to fetch personalized data associated with one or more users by their User IDs. The node batches requests for efficiency and supports retrying failed batch requests.
Common scenarios where this node is beneficial include:
- Personalizing content or product recommendations based on stored user attributes.
- Fetching user metadata or preferences to tailor marketing campaigns.
- Integrating user profile data into workflows for analytics or decision-making.
For example, you might use this node to get preference scores or behavioral metrics for a list of users, then use that data downstream to customize email content or website experiences.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the user whose values you want to retrieve. |
| Max Retries | Number of times to retry failed batch requests (default is 2). |
Output
The node outputs an array of JSON objects, each corresponding to an input item/user. Each output object contains:
success: A boolean indicating if the request for that user succeeded.userId: The User ID requested.userData: The retrieved user values from Recombee (present only if successful).error: Error message if the request failed (present only if unsuccessful).
If the node is configured to continue on failure, it will include error details per failed user without stopping execution.
No binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the Recombee service.
- Needs configuration of database ID, private token, and region for the Recombee API client.
- Uses the official Recombee API client library (
recombee-api-client).
Troubleshooting
Common issues:
- Invalid or missing User ID will cause errors.
- Network or API rate limiting errors may occur; the node retries failed batch requests up to the configured max retries.
- If the Recombee credentials are incorrect or expired, authentication errors will be thrown.
Error messages:
- Errors returned from the Recombee API are surfaced in the output per user.
- If not continuing on fail, any error will stop execution and throw a node operation error.
Resolutions:
- Verify User IDs are correct and exist in the Recombee database.
- Check API credentials and permissions.
- Increase "Max Retries" if transient network issues occur.
- Enable "Continue On Fail" to handle partial failures gracefully.