Overview
This node creates a new customer record in the Omniwallet system via its API. It is useful for automating customer management workflows, such as adding new customers from form submissions, CRM exports, or other data sources directly into Omniwallet without manual entry.
Practical examples include:
- Automatically creating customer profiles when users sign up on a website.
- Importing customer data from external systems to Omniwallet.
- Enriching customer records with loyalty points and membership levels programmatically.
Properties
| Name | Meaning |
|---|---|
| Customer's email address (required). | |
| Name | Customer's first name (required). |
| Last Name | Customer's last name (optional). |
| Phone | Customer's phone number (optional). |
| Level | Customer's membership or status level (optional). |
| Points | Loyalty or reward points assigned to the customer (optional, default is 0). |
| Card | Customer's card number; if left empty, the system generates one automatically. |
Output
The node outputs an array of JSON objects, each representing the created customer data returned by the Omniwallet API. The main output field json contains the customer information under a data property, which includes attributes like email, name, last name, phone, level, points, and card number.
If the creation fails for any item and the node is set to continue on failure, the output for that item will contain an error field with the error message.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the Omniwallet API.
- Needs an API authentication credential configured in n8n to authorize requests.
- The node uses a helper function (
omniwalletApiRequest) to perform HTTP POST requests to the/customersendpoint.
Troubleshooting
Common issues:
- Missing required fields like Email or Name will cause the API request to fail.
- Invalid or expired API credentials will result in authentication errors.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Errors returned from the API are captured and included in the output if "Continue On Fail" is enabled.
- Typical error messages might indicate invalid input data or authorization failures.
Resolution tips:
- Ensure all required properties are provided and correctly formatted.
- Verify that the API key or token used has sufficient permissions.
- Check network access and Omniwallet service status.
Links and References
- Omniwallet API documentation (refer to the official Omniwallet developer portal for detailed API specs).
- n8n documentation on creating custom nodes and handling API credentials.