Recombee AddItem
Overview
This node adds new items to a Recombee recommendation catalog. Each item is identified by a unique string ID, which allows the Recombee system to track and recommend items based on user interactions. This operation is essential for building and maintaining an up-to-date item catalog in Recombee, enabling item-based recommendations.
Typical use cases include:
- Adding new products to an e-commerce recommendation engine.
- Registering new content items (e.g., articles, videos) for personalized suggestions.
- Updating the catalog with new entries in batch workflows.
For example, when a new product is added to an online store, this node can be used to register that product in Recombee so it becomes available for recommendation algorithms.
Properties
| Name | Meaning |
|---|---|
| Item ID | Unique identifier for the item. Can contain digits, Latin letters, underscores, colons, minus signs, at signs, and dots. |
| Max Retries | Number of times to retry failed batch requests. Useful for handling temporary network issues or rate limits. |
Output
The node outputs an array of JSON objects, each corresponding to an input item processed:
success: Boolean indicating if the item was successfully added.itemId: The unique identifier of the item attempted to add.data: Contains the response data from Recombee for successful additions.error: If the addition failed, contains the error message explaining why.
If the node is configured to continue on failure, errors for individual items are included in the output without stopping the entire execution. Otherwise, the node throws an error on the first failure.
No binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the Recombee service.
- Needs configuration of the Recombee database ID, private token, and region via credentials.
- Uses the official Recombee API client library to communicate with the Recombee service.
Troubleshooting
Common Issues:
- Invalid or missing item IDs may cause errors.
- Network issues or rate limiting can cause batch request failures.
- Incorrect or expired API credentials will prevent successful communication.
Error Messages:
- Errors returned from Recombee API are surfaced in the output or thrown as exceptions.
- If retries exceed the configured maximum, the node throws an error unless "continue on fail" is enabled.
Resolutions:
- Verify that item IDs conform to allowed characters.
- Check API credentials and permissions.
- Increase "Max Retries" to handle transient network problems.
- Enable "continue on fail" to process other items even if some fail.