Actions19
- Customer Actions
- Subscription Actions
- Invoice Actions
Overview
The node integrates with the ProAbono API to create or update customer records. It is designed to manage customer data within a subscription billing context, allowing users to add new customers or modify existing ones based on a unique reference identifier.
Common scenarios include:
- Adding new customers to a billing system.
- Updating customer details such as name, email, language preference, or affiliation information.
- Associating customers with specific segments for targeted subscription management.
Practical example:
A business wants to onboard a new customer named "John Doe" with an email address and assign them to a particular segment for subscription offers. This node can be used to send that data to ProAbono, ensuring the customer is created or updated accordingly.
Properties
| Name | Meaning |
|---|---|
| Name | The full name of the customer (e.g., "John Doe"). |
| The customer's email address, automatically converted to lowercase before sending (e.g., "[email protected]"). | |
| Reference Customer | A unique identifier for the customer used internally in your application; required for identifying the customer record. |
| Language | The preferred language code of the customer (e.g., "fr" for French). See ProAbono Language Codes for valid values. |
| Reference Affiliation | Additional affiliation information about the customer, such as an IP address or reseller name. |
| Segment Name or ID | The segment to which the customer belongs. Can be selected from a list or specified by ID using expressions. This categorizes the customer for subscription purposes. |
Output
The node outputs JSON data representing the response from the ProAbono API after creating or updating the customer. This typically includes confirmation of the customer record's creation or update status and may contain the customer's details as stored in ProAbono.
No binary data output is involved.
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 the ProAbono API endpoints for customer management.
Troubleshooting
- Authentication errors: Ensure that the API keys and business ID are correctly configured in the node credentials. Invalid or missing credentials will cause authorization failures.
- Missing required fields: The "Name", "Reference Customer", and "Segment Name or ID" properties are mandatory. Omitting these will result in validation errors.
- Invalid language codes: Using unsupported language codes may cause the API to reject the request. Refer to the official language codes documentation.
- Segment loading issues: If the segment list fails to load, verify network connectivity and API permissions.
- Email formatting: The email is converted to lowercase automatically; ensure the input is a valid email format to avoid API rejections.
Links and References
- ProAbono API Documentation - Languages
- n8n Expressions Documentation (for specifying dynamic segment IDs)