Actions19
- Customer Actions
- Subscription Actions
- Invoice Actions
Overview
This node integrates with the ProAbono API to update the payment settings of a customer identified by a unique reference within your own application. It allows you to specify how the customer will be billed, including the payment method type, the date for the next billing, and whether recurring billing is enabled.
Common scenarios where this node is beneficial include:
- Automating updates to customer payment preferences in your billing system.
- Switching customers between different payment methods such as bank transfer, check, or cash.
- Scheduling the next billing date programmatically.
- Enabling or disabling automatic recurring billing for customers.
For example, if you want to change a customer's payment method to wire transfer and set their next billing date to a specific day while enabling auto-billing, this node can perform that update seamlessly via the ProAbono API.
Properties
| Name | Meaning |
|---|---|
| Reference Customer | The unique identifier used within your own application to identify the customer whose payment settings are being updated. |
| Type Payment | The payment method type for the customer. Options: Wire/Bank Transfer, Check, Cash, Other. |
| Date Next Billing | The date when the next billing should occur for the customer. |
| Enable Recurring Billing? | Whether automatic recurring billing is enabled for the customer. Options: Yes (auto billing enabled), No (manual billing). |
Output
The node outputs JSON data representing the response from the ProAbono API after updating the customer's payment settings. This typically includes confirmation of the updated fields and any relevant metadata returned by the API.
If the API supports binary data output (not indicated here), it would represent related files or documents, but this node primarily deals with JSON responses.
Dependencies
- Requires an active ProAbono API account.
- Needs API authentication credentials: an agent key and an API key.
- Requires configuration of the business ID to construct the correct API base URL.
- The node depends on the ProAbono API endpoint at
https://api-{businessId}.proabono.com/v1.
Troubleshooting
- Invalid Reference Customer: If the provided customer reference does not exist, the API may return an error indicating the customer was not found. Verify the reference ID is correct.
- Authentication Errors: Incorrect or missing API keys will cause authentication failures. Ensure valid credentials are configured.
- Invalid Date Format: The "Date Next Billing" must be a valid datetime; otherwise, the API may reject the request.
- Unsupported Payment Type: Selecting a payment type outside the allowed options will result in errors. Use one of the predefined types.
- Auto Billing Flag Issues: The "Enable Recurring Billing?" property expects a boolean-like string ("true" or "false"). Providing other values may cause unexpected behavior.