Actions19
- Customer Actions
- Subscription Actions
- Invoice Actions
Overview
This node integrates with the ProAbono API to manage subscription-related operations. Specifically, for the "Subscription" resource and the "Start a Subscription" or "Restart a Subscription" operations, it allows users to initiate or restart an existing subscription by specifying its ID. This is useful in scenarios where you need to programmatically control subscription lifecycles, such as automating subscription activations after payment confirmation or reactivating subscriptions that were previously suspended.
Practical examples:
- Automatically start a subscription when a customer completes a signup process.
- Restart a subscription that was paused due to non-payment once the payment is received.
Properties
Name | Meaning |
---|---|
Subscription ID | The unique numeric identifier of the subscription to start or restart. This must be provided to specify which subscription the operation applies to. |
Output
The node outputs JSON data representing the result of the subscription start or restart operation as returned by the ProAbono API. This typically includes details about the subscription status, identifiers, timestamps, and any relevant metadata confirming the action taken.
If the node supports binary data output (not indicated in the provided code), it would represent associated files or documents related to the subscription, but no such indication is present here.
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 from credentials.
- Proper configuration of these credentials within n8n is necessary for successful API communication.
Troubleshooting
- Invalid Subscription ID: If the provided subscription ID does not exist or is incorrect, the API will likely return an error indicating the subscription was not found. Verify the ID before running the node.
- Authentication Errors: Missing or incorrect API keys or business ID will cause authentication failures. Ensure credentials are correctly set up.
- Network Issues: Connectivity problems can prevent the node from reaching the ProAbono API endpoint.
- Operation Not Allowed: Attempting to start or restart a subscription that is already active or in an incompatible state may result in errors. Check the subscription status before performing the operation.
Links and References
- ProAbono API Documentation (general reference for API endpoints and usage)
- n8n documentation on Credentials for setting up API keys and authentication