Overview
This node updates an existing customer record in the Omniwallet system via its API. 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 updating loyalty program details.
For example, if a customer's phone number or loyalty points change, this node can update those fields in Omniwallet automatically.
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 an array of JSON objects representing the updated customer data returned by the Omniwallet API. Each output item corresponds to one input item and contains the updated customer information under the json field.
If the update fails for any item and the node is set to continue on failure, the output will contain an error object with the error message, the index of the failed item, and the email used for that update attempt.
No binary data is produced by this node.
Dependencies
- Requires an API key credential for authenticating requests to the Omniwallet API.
- The node uses the PATCH HTTP method to update customer data at the endpoint
/customers/{customerEmail}. - Proper configuration of the API credential within n8n is necessary for successful execution.
Troubleshooting
- Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing an incorrect or non-existent customer email will result in errors from the API indicating the customer was not found.
- Network connectivity problems may cause request timeouts or failures.
- Error messages:
- Errors thrown by the API are captured and returned in the output if "Continue On Fail" is enabled.
- Typical error messages might include "Customer not found" or "Invalid API key".
- Resolution tips:
- Verify the API credential is correctly configured and active.
- Ensure the customer email exists in the Omniwallet system before attempting an update.
- Check network connectivity and retry if transient errors occur.
Links and References
- Omniwallet API documentation (for customer update endpoint) — consult your Omniwallet API docs for detailed request/response formats and authentication setup.