Overview
This node retrieves customer information from the Omniwallet API by using a customer's email address. It is designed to fetch detailed data about a specific customer, which can be useful in workflows that require customer verification, profile enrichment, or integration with other systems based on customer identity.
Practical examples include:
- Automatically pulling customer details when an email is provided during a support ticket creation.
- Enriching CRM records with up-to-date customer data from Omniwallet.
- Validating customer existence before processing orders or transactions.
Properties
| Name | Meaning |
|---|---|
| Customer Email | The email address of the customer to retrieve from Omniwallet. This must be a valid email string. |
Output
The node outputs an array of JSON objects, each representing the retrieved customer data corresponding to the input email(s). The main output field json contains the customer information as returned by the Omniwallet API under the data property. If no data property exists, it returns the full response object.
In case of errors (e.g., customer not found), the output JSON will contain an error field with the error message, along with the original input email and item index for reference.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the Omniwallet API via an API key credential configured in n8n.
- The node depends on a helper function (
omniwalletApiRequest) to make authenticated HTTP requests to the Omniwallet API.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing an incorrect or non-existent email will result in an error response from the API.
- Network connectivity problems may prevent successful API calls.
Error messages:
- Errors returned from the API are captured and included in the output JSON under the
errorfield. - If the node is set to continue on failure, it will output the error per item; otherwise, it will stop execution and throw the error.
- Errors returned from the API are captured and included in the output JSON under the
Resolution tips:
- Verify that the API key credential is correctly set up and has necessary permissions.
- Ensure the email input is correctly formatted and corresponds to an existing customer.
- Check network connectivity and API endpoint availability.
Links and References
- Omniwallet API Documentation (replace with actual URL if available)
- n8n documentation on creating custom nodes