Actions19
- Customer Actions
- Subscription Actions
- Invoice Actions
Overview
The node integrates with the ProAbono API to manage subscription-related data. Specifically, for the "Retrieve a Subscription" operation, it fetches detailed information about a specific subscription by its ID. This is useful in scenarios where you need to access subscription details such as status, plan, or customer association within an automation workflow.
Practical examples include:
- Automatically retrieving subscription details when a new order is placed.
- Checking subscription status before performing billing or support actions.
- Syncing subscription data with other systems like CRMs or accounting software.
Properties
| Name | Meaning |
|---|---|
| Subscription ID | The unique numeric identifier of the subscription to retrieve. This is required to specify which subscription's details to fetch. |
Output
The node outputs JSON data representing the subscription details retrieved from the ProAbono API. This typically includes fields such as subscription ID, status, associated customer, plan details, start and end dates, and any other metadata provided by the API.
If the API supports binary data related to subscriptions (e.g., attached documents), the node would handle that accordingly, but based on the provided code and properties, the output focuses on JSON subscription data.
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.
- Proper configuration of these credentials in n8n is necessary for successful API communication.
Troubleshooting
- Missing or invalid Subscription ID: Ensure the Subscription ID property is set and is a valid number; otherwise, the API call will fail.
- Authentication errors: Verify that the API keys and business ID are correctly configured in the node credentials.
- Network or API errors: Check network connectivity and confirm the ProAbono service is operational.
- Incorrect resource or operation selection: Make sure the resource is set to "Subscription" and the operation to "Retrieve a Subscription" to match this functionality.
Common error messages may include unauthorized access, not found errors if the subscription ID does not exist, or validation errors for missing parameters.
Links and References
- ProAbono API Documentation (general reference for API endpoints and data structures)
- n8n documentation on creating custom nodes for further customization guidance