Overview
This node updates an existing customer record in the Omniwallet API system. It is designed to modify customer details such as name, contact information, membership level, points, and card number. This node is useful in scenarios where customer data needs to be kept current, for example, updating a customer's phone number after they provide a new one, adjusting loyalty points after a purchase, or correcting personal details.
Practical examples include:
- Synchronizing customer information from a CRM system to Omniwallet.
- Automatically updating customer levels based on recent activity.
- Assigning or regenerating card numbers for customers.
Properties
| Name | Meaning |
|---|---|
| Customer Email | Email of the customer to update (used as unique identifier for the customer record). |
| Name | First name of the customer. |
| Last Name | Last name of the customer. |
| Phone | Phone number of the customer. |
| Level | Customer level (e.g., membership tier or status). |
| Points | Number of loyalty or reward points assigned to the customer. |
| Card | Card number associated with the customer; if left empty, a card number will be auto-generated. |
Output
The node outputs JSON data representing the updated customer object returned by the Omniwallet API. The output structure includes the updated attributes of the customer such as name, last name, phone, level, points, and card number.
If an error occurs during the update and the node is configured to continue on failure, the output JSON will contain an error field with the error message, the index of the item that caused the error, and the email of the customer attempted to update.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating requests to the Omniwallet API.
- The node uses a PATCH HTTP method to update customer data at the endpoint
/customers/{customerEmail}. - Proper configuration of the API credential within n8n is necessary for successful operation.
Troubleshooting
Common issues:
- Invalid or missing customer email will cause the API request to fail since the email identifies the customer to update.
- Providing invalid data types (e.g., non-numeric points) may result in API errors.
- Network or authentication failures can prevent the update from succeeding.
Error messages:
- Errors returned from the API are captured and can be output if "Continue On Fail" is enabled.
- Typical error messages might include "Customer not found" if the email does not exist in the system, or "Unauthorized" if the API credentials are incorrect.
Resolutions:
- Verify the customer email exists in Omniwallet before attempting an update.
- Ensure all required fields are provided and correctly formatted.
- Check API credentials and network connectivity.
Links and References
- Omniwallet API documentation (refer to the official Omniwallet API docs for detailed information on customer endpoints and authentication).
- n8n documentation on creating and using API credentials.
- General REST API usage guidelines for PATCH requests.