Recombee ListUserViewPortionsInstall

Overview

This node, "Recombee ListUserViewPortions," retrieves the portions of content viewed by a specific user from a Recombee recommendation database. It is useful in scenarios where you want to analyze or act upon the viewing history of users, such as personalizing recommendations, tracking user engagement, or generating reports on user activity.

For example, an e-commerce platform could use this node to fetch which product portions a user has viewed to tailor future product suggestions. Similarly, a media streaming service might track watched segments of videos to resume playback or recommend related content.

Properties

Output

The node outputs an array of JSON objects, each representing the result of a request for a user's viewed portions. Each output item contains:

• success: A boolean indicating if the request was successful.
• If successful:
  • The original input parameters (e.g., userId).
  • userData: The data returned by Recombee about the user's viewed portions.
• If failed:
  • error: The error message explaining why the request failed.
  • The original input parameters.

The output preserves the order and pairing with input items, allowing correlation between requests and responses.

No binary data is produced 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 recombee-api-client library to communicate with the Recombee API.
• Supports a configurable timeout for API requests, defaulting to 10 seconds if not specified.

Troubleshooting

• Common Issues:

  • Network failures or rate limiting may cause batch requests to fail.
  • Invalid or missing user IDs will result in errors from the Recombee API.
  • Incorrect or expired API credentials will prevent successful authentication.

• Error Handling:

  • The node retries failed batch requests up to the configured "Max Retries" count.
  • If "Continue On Fail" is enabled, errors for individual requests are captured in the output without stopping execution.
  • Without "Continue On Fail," the node throws an error immediately on failure.

• Resolution Tips:

  • Verify that the user IDs provided are valid and exist in the Recombee database.
  • Ensure API credentials are correctly set and have sufficient permissions.
  • Increase "Max Retries" if transient network issues are common.
  • Enable "Continue On Fail" to allow partial success when processing multiple users.

Links and References

• Recombee API Documentation
• n8n Node Development Guide