Actions19
- Customer Actions
- Subscription Actions
- Invoice Actions
Overview
This node integrates with the ProAbono API to update the billing address information of a customer identified by a unique reference within your own application. It is useful in scenarios where you need to keep customer billing details synchronized between your system and ProAbono, such as when customers update their address or company information.
Practical examples include:
- Automatically updating a customer's billing address after they submit a change form on your website.
- Synchronizing billing details from your CRM or ERP system to ProAbono for accurate invoicing.
- Correcting or completing missing billing information before generating invoices.
Properties
Name | Meaning |
---|---|
Reference Customer | The unique identifier used within your own application to identify the customer whose billing address will be updated. (Required) |
Company | The company name associated with the billing address. |
First Name | The first name of the contact person for the billing address. |
Last Name | The last name of the contact person for the billing address. |
Address Line 1 | The primary street address line for the billing address. |
Address Line 2 | The secondary street address line (e.g., apartment, suite, floor). |
City | The city of the billing address. |
ZIP Code | The postal or ZIP code of the billing address. |
Country | The country code of the billing address, using ISO 3166-1 Alpha-2 format (e.g., "FR" for France). |
Region | The region, state, or province code of the billing address, using ISO 3166-2 format (e.g., "FR-75"). |
Tax Information | Tax-related information such as VAT number or other tax identifiers relevant to the billing address. |
Phone | Phone number associated with the billing address. |
Output
The node outputs JSON data representing the updated customer billing address as returned by the ProAbono API. This typically includes confirmation of the updated fields and possibly the full customer record with the new billing address details.
If the node supports binary data output, it would relate to any files or documents returned by the API, but based on the provided code and properties, this operation focuses on JSON data only.
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
- Authentication errors: Ensure that the API keys and business ID are correctly configured and have the necessary permissions.
- Invalid Reference Customer: If the provided customer reference does not exist in ProAbono, the API may return an error indicating the customer was not found.
- Invalid country or region codes: Use correct ISO codes for country and region to avoid validation errors.
- Missing required fields: The Reference Customer field is mandatory; omitting it will cause the request to fail.
- Network issues: Verify network connectivity and that the ProAbono API endpoint is reachable.
Links and References
- ProAbono API Documentation (general reference for API endpoints and data formats)
- ISO 3166-1 Alpha-2 Country Codes
- ISO 3166-2 Region Codes