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, loyalty level, points, or card number. Typical scenarios include syncing updated 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 automatically.
Properties
| Name | Meaning |
|---|---|
| Customer Email | Email of the customer to update (used as unique identifier for the customer record). |
| Name | Customer's first name. |
| Last Name | Customer's last name. |
| Phone | Customer's phone number. |
| Level | Customer's loyalty or membership level. |
| Points | Number of loyalty points the customer has. |
| Card | Card number associated with the customer; leave empty to auto-generate a new card. |
Output
The node outputs JSON data representing the updated customer object returned by the Omniwallet API. The structure typically includes the updated customer attributes such as name, last name, phone, level, points, and card number.
If an error occurs during update and "Continue On Fail" is enabled, the output will contain an error message along with the item index and the email of the customer that failed to update.
No binary data is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Omniwallet API.
- The node makes HTTP PATCH requests to the
/customers/{email}endpoint of the Omniwallet API. - Proper network access to the Omniwallet API endpoint is necessary.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing an incorrect or non-existent customer email will result in errors since the customer cannot be found.
- Improperly formatted input data (e.g., invalid email format) may cause the API to reject the request.
Error messages:
- Errors returned from the API are passed through. For example, "Customer not found" indicates the email does not match any existing record.
- Network or timeout errors indicate connectivity issues.
Resolutions:
- Verify API credentials are correctly configured.
- Ensure the customer email exists in Omniwallet before attempting an update.
- Validate all input fields conform to expected formats.
- Enable "Continue On Fail" to allow processing of multiple items even if some fail.
Links and References
- Omniwallet API documentation (refer to the official Omniwallet API docs for detailed endpoint and data schema information).