Overview
This node updates an existing customer record in the Omniwallet API system. It is useful when you need to modify customer details such as name, contact information, membership level, points, or card number. Typical scenarios include synchronizing customer data from other systems, correcting customer information, or managing loyalty program details.
For example, if a customer's phone number or loyalty points change, this node can update those fields in Omniwallet to keep records current.
Properties
| Name | Meaning |
|---|---|
| Customer Email | Email of the customer to update (used as the unique identifier for the customer record) |
| Name | Customer's first name |
| Last Name | Customer's last name |
| Phone | Customer's phone number |
| Level | Customer membership or status level |
| Points | Number of loyalty or reward points the customer has |
| Card | Card number associated with the customer; leave empty to auto-generate a new card number |
Output
The node outputs JSON data representing the updated customer object returned by the Omniwallet API. The output structure includes the updated customer attributes such as name, last name, phone, level, points, and card number.
If the update fails and "Continue On Fail" is enabled, the output will contain an error message along with the item index and customer email that caused the failure.
Dependencies
- Requires an API key credential for authenticating requests to the Omniwallet API.
- Uses the PATCH HTTP method to update customer data at the endpoint
/customers/{customerEmail}. - The node depends on a helper function (
omniwalletApiRequest) to make authenticated API calls.
Troubleshooting
Common issues:
- Invalid or missing customer email will cause the API request to fail because the email identifies which customer to update.
- Providing invalid data types (e.g., non-numeric points) may result in API errors.
- Network or authentication failures will prevent successful updates.
Error messages:
- If the API returns an error, it will be included in the output JSON under the
errorfield if "Continue On Fail" is enabled. - Common errors might include "Customer not found" if the email does not exist, or "Unauthorized" if the API key is invalid.
- If the API returns an error, it will be included in the output JSON under the
Resolution:
- Verify the customer email exists in Omniwallet before updating.
- Ensure all required fields are provided and correctly formatted.
- Check that the API key credential is valid and has necessary permissions.
Links and References
- Omniwallet API documentation (refer to the official Omniwallet API docs for detailed info on customer endpoints)
- n8n documentation on creating and using credentials and API nodes