Actions19
- Customer Actions
- Subscription Actions
- Invoice Actions
Overview
The node integrates with the ProAbono API to manage subscription-related operations, specifically allowing users to add usage quantities to a feature within a customer's subscription. This is useful in scenarios where subscription features are metered or usage-based, and you need to increment the recorded usage quantity dynamically.
For example, if you have a SaaS product that charges customers based on API calls or data consumption, this node can be used to update the usage count each time the customer consumes more resources, ensuring accurate billing and feature tracking.
Properties
| Name | Meaning |
|---|---|
| Reference Customer | The unique identifier for the customer within your own application. This identifies which customer's subscription to update. |
| Reference Feature | The specific feature of the subscription to which usage quantity will be added. You can select from a list of available features or specify one using an expression. |
| Increment | The numeric amount by which to increase the current usage quantity of the specified feature. |
Output
The node outputs JSON data representing the result of the API call to add usage quantity. This typically includes confirmation of the updated usage, details about the subscription feature, and any relevant metadata returned by the ProAbono API.
No binary data output is indicated.
Dependencies
- Requires an active connection to the ProAbono API.
- Needs credentials including a business identifier, an agent key, and an API key for authentication.
- The base URL for API requests is dynamically constructed using the business ID credential.
- The node depends on internal methods to load options for features (
getFeatures), which fetches available subscription features dynamically.
Troubleshooting
- Authentication errors: Ensure that the API keys and business ID credentials are correctly configured and valid.
- Invalid Reference Customer or Feature: If the provided customer ID or feature reference does not exist or is incorrect, the API will likely return an error. Verify these values before execution.
- Increment value issues: The increment must be a valid number; non-numeric or missing values may cause request failures.
- API connectivity problems: Network issues or incorrect base URL formation (due to wrong business ID) can prevent successful API calls.
Links and References
- ProAbono API Documentation (general reference for API endpoints and usage)
- n8n Expressions Documentation (for using expressions in property fields)