Actions38
- Attribute Actions
- Customer Actions
- Entitlement Actions
- Feature Actions
- Product Actions
- Local License Server Actions
- Offering Actions
- Plan Actions
Overview
The node "Nalpeiron Zentitle2" is designed to interact with the Nalpeiron Zentitle2 API, specifically for managing product-related data. In the context of the "Product" resource and the "Get Product" operation, this node retrieves detailed information about a specific product identified by its Product ID.
This node is beneficial in scenarios where users need to programmatically access product details from the Nalpeiron Zentitle2 platform, such as integrating product data into workflows, automating reporting, or synchronizing product information with other systems.
Example use case:
A software vendor wants to automatically fetch product details from their Nalpeiron account whenever a new order is processed, enabling them to verify product configurations or licensing information before fulfillment.
Properties
| Name | Meaning |
|---|---|
| Product ID | The unique identifier of the product to retrieve. This is a required string input. |
Output
The node outputs JSON data containing the details of the requested product. The exact structure depends on the Nalpeiron Zentitle2 API response for the product retrieval endpoint but typically includes fields such as product name, description, attributes, editions, features, and other metadata related to the product.
If the node supports binary data output (not evident from the provided code), it would represent any associated files or attachments related to the product, but this is not indicated here.
Dependencies
- Requires an API key credential for authenticating with the Nalpeiron Zentitle2 API.
- Needs configuration of the base URL and tenant ID via credentials or environment variables.
- Relies on internal modules for property definitions and request coordination (
property-registryandnode-coordinator).
Troubleshooting
Common issues:
- Missing or invalid Product ID will cause the API call to fail.
- Incorrect or missing API credentials will result in authentication errors.
- Network connectivity problems can prevent successful API communication.
Error messages:
- Authentication failures typically indicate invalid or expired API keys; ensure credentials are correctly configured.
- "Product not found" errors suggest the provided Product ID does not exist; verify the ID is correct.
- Timeout or connection errors may require checking network settings or API availability.
Links and References
- Nalpeiron Zentitle2 API Documentation (general reference for API endpoints and data structures)
- n8n documentation on creating custom nodes for further customization guidance