Overview
This node, named "Get Information of Product - UNEXO," is designed to retrieve detailed information about products for specific users. It takes user data from the input and combines it with a product ID to query an external API endpoint that returns product-related information in batch. This node is useful in scenarios where you want to enrich user data with product details, such as in marketing automation, customer analytics, or personalized recommendations.
For example, if you have a list of users and want to know their interaction or status with a particular product, this node can fetch that information efficiently by sending a batch request to the external service.
Properties
| Name | Meaning |
|---|---|
| Product ID | The identifier of the product for which information is requested. |
| Users | A string representing users; if left blank, the node uses users from the previous node. |
Output
The node outputs a JSON array containing the response from the external API. Each element corresponds to the product information related to the users and product IDs sent in the request. The exact structure depends on the external API's response but generally includes product details linked to each user.
No binary data output is produced by this node.
Dependencies
- Requires an environment variable
CDP_URLthat specifies the base URL of the external API. - Requires an environment variable
UNEXO_API_KEYused as a Bearer token for authorization when calling the API. - The node makes an HTTP POST request to the endpoint
${CDP_URL}/api/users/GetProductsInfoBatch.
Troubleshooting
- Missing or incorrect environment variables: If
CDP_URLorUNEXO_API_KEYare not set or invalid, the node will fail to authenticate or reach the API. Ensure these are correctly configured in your n8n environment. - Empty or invalid Product ID: Providing an empty or invalid product ID may result in no data or errors from the API.
- Input data format: The node expects the input items to contain a JSON property
anonymousIds(an array) and optionallyoutputResult. If these are missing or malformed, the request payload may be incorrect, causing API errors. - API errors: Any HTTP error responses from the external API should be checked for details. Common issues include rate limiting, invalid tokens, or malformed requests.
Links and References
- No direct links provided in the source code. For more information, consult the documentation of the external API at the URL specified by
CDP_URL.