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, enabling users to interact programmatically with product licensing and entitlement data managed by Nalpeiron. Specifically, for the Product resource and the Get Product Editions Features operation, it retrieves detailed information about features associated with a particular edition of a product.
Common scenarios where this node is beneficial include:
- Automating license management workflows by fetching feature entitlements for specific product editions.
- Integrating product feature data into internal dashboards or reporting tools.
- Validating feature availability before provisioning software capabilities to end-users.
For example, a software vendor could use this node to query which features are enabled in a customer's licensed edition of their product, then tailor the user experience accordingly.
Properties
| Name | Meaning |
|---|---|
| Product ID | The unique identifier of the product for which you want to retrieve edition features. |
| Edition ID | The unique identifier of the product edition whose features you want to fetch. |
| Feature ID | The unique identifier of the specific feature within the edition to retrieve information about. |
Output
The node outputs JSON data representing the features associated with the specified product edition. This typically includes details such as feature identifiers, names, descriptions, and possibly status or entitlement information depending on the API response.
If binary data were involved (e.g., license files), it would be included in a separate binary output field, but based on the provided code and operation, the output is purely JSON.
Dependencies
- Requires an active connection to the Nalpeiron Zentitle2 API.
- Needs an API authentication token credential configured in n8n to authorize requests.
- The base URL for the API can be customized via credentials; otherwise, it defaults to
https://api.nalpeiron.com. - The node sets necessary HTTP headers including content type and tenant identification from credentials.
Troubleshooting
- Missing or invalid API credentials: Ensure that the API key/token and tenant ID are correctly set in the node's credentials configuration.
- Invalid Product, Edition, or Feature IDs: Double-check that the IDs provided exist and are correct; otherwise, the API may return errors or empty results.
- Network connectivity issues: Verify that your environment can reach the Nalpeiron API endpoint.
- API rate limits or permission errors: Confirm that your API credentials have sufficient permissions and that you are not exceeding usage limits.
Common error messages might include unauthorized access, resource not found, or bad request due to missing parameters. Resolving these usually involves verifying input properties and credential settings.