Actions38
- Attribute Actions
- Customer Actions
- Entitlement Actions
- Feature Actions
- Product Actions
- Local License Server Actions
- Offering Actions
- Plan Actions
Overview
This node integrates with the Nalpeiron Zentitle2 API, specifically to retrieve product-related data such as product features. The "Get Product Features" operation fetches detailed information about specific features associated with a given product. This is useful in scenarios where you need to programmatically access licensing or feature details of software products managed via Nalpeiron's platform.
Practical examples include:
- Automatically retrieving and displaying feature sets for a product in a dashboard.
- Integrating product feature data into other systems for reporting or license management.
- Validating feature availability before enabling functionality in an application.
Properties
| Name | Meaning |
|---|---|
| Product ID | The unique identifier of the product for which features are being retrieved. |
| Feature ID | The unique identifier of the specific feature within the product to get details for. |
Output
The node outputs JSON data representing the requested product feature(s). The structure typically includes details such as feature identifiers, names, descriptions, and possibly status or configuration related to the feature within the product context.
If binary data were involved (not indicated here), it would represent files or attachments related to the product features, but this node focuses on JSON responses from the API.
Dependencies
- Requires an API key credential for authenticating with the Nalpeiron Zentitle2 API.
- Needs configuration of the base URL and tenant ID, usually provided through credentials.
- Relies on the external Nalpeiron Zentitle2 REST API endpoint (
https://api.nalpeiron.comby default).
Troubleshooting
- Missing or invalid API credentials: Ensure that the API key and tenant ID are correctly configured in the node credentials.
- Invalid Product ID or Feature ID: Verify that the IDs provided exist and are correct; otherwise, the API may return errors or empty results.
- Network issues or incorrect base URL: Confirm network connectivity and that the base URL is accurate if customized.
- API rate limits or permission errors: Check API usage limits and permissions associated with the API key.
Common error messages might include authentication failures, resource not found, or bad request errors due to missing parameters. Resolving these involves verifying input properties and credential configurations.
Links and References
- Nalpeiron Zentitle API Documentation (general reference for API endpoints and usage)
- n8n documentation on creating custom nodes for further customization guidance