Actions38
- Attribute Actions
- Customer Actions
- Entitlement Actions
- Feature Actions
- Product Actions
- Local License Server Actions
- Offering Actions
- Plan Actions
Overview
The node "Nalpeiron Zentitle2" provides integration with the Nalpeiron Zentitle2 API, enabling users to interact programmatically with entitlement-related data. Specifically, for the "Entitlement" resource and the "List Entitlement Activations" operation, this node fetches a list of activations associated with a given entitlement ID.
This functionality is useful in scenarios where software vendors or license managers want to retrieve activation details for a particular entitlement, such as tracking how many times a license has been activated, managing license usage, or auditing activations for compliance purposes.
Practical examples include:
- Retrieving all activation records for a specific software license entitlement.
- Monitoring active installations linked to an entitlement.
- Generating reports on license usage based on activation data.
Properties
| Name | Meaning |
|---|---|
| Entitlement ID | The unique identifier of the entitlement for which to list activations. This is a required string input. |
Output
The node outputs JSON data representing the list of entitlement activations retrieved from the Nalpeiron Zentitle2 API. The structure typically includes activation records related to the specified entitlement ID, containing details such as activation timestamps, device information, user data, or other metadata provided by the API.
If the API supports binary data (e.g., attachments or logs), the node would handle it accordingly, but based on the provided code and context, the output focuses on JSON-formatted activation data.
Dependencies
- Requires an API key credential for authenticating with the Nalpeiron Zentitle2 API.
- The base URL for the API can be configured via credentials; defaults to
https://api.nalpeiron.com. - Requires setting a tenant ID in the request headers through credentials.
- Uses internal helper modules for property definitions and execution coordination.
Troubleshooting
- Missing or invalid Entitlement ID: Since the entitlement ID is required, ensure it is provided and correctly formatted. Errors may occur if this parameter is empty or incorrect.
- Authentication errors: Verify that the API key credential and tenant ID are correctly configured and valid.
- Network or API endpoint issues: Confirm that the base URL is reachable and the API service is operational.
- Permission issues: Ensure the API key has sufficient permissions to access entitlement activation data.
- Unexpected response format: If the API changes its response schema, the node might not parse the output correctly.
Links and References
- Nalpeiron Zentitle API Documentation (general reference for API endpoints and authentication)
- n8n documentation on Creating Custom Nodes