Overview
This node, named "Omniwallet - Get Customer by Email Tool," is designed to retrieve detailed information about a specific customer from the Omniwallet API using their email address. It is useful in scenarios where you need to fetch customer data dynamically based on an email input, such as verifying customer details before processing transactions, syncing customer records, or integrating customer information into workflows.
Practical examples include:
- Automatically fetching customer profiles during payment processing.
- Validating customer existence and details before sending marketing emails.
- Integrating with CRM systems to update or enrich customer data based on email lookups.
Properties
| Name | Meaning |
|---|---|
| Customer Email | The email address of the customer to retrieve from the Omniwallet system. This must be a valid email string (e.g., "customer@example.com"). |
Output
The node outputs an array of JSON objects, each representing the retrieved customer data corresponding to the provided email address. The structure of the json output field contains the customer information returned by the Omniwallet API under the data property. If no data property exists, it returns the entire response object.
In case of errors (e.g., customer not found or API issues), the output includes an error object with the error message, the index of the item that caused the error, and the email used for the lookup.
The node does not output binary data.
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. - Proper network access to the Omniwallet API endpoint is necessary.
Troubleshooting
Common Issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing an incorrectly formatted email may result in no customer being found or API 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 include "Customer not found" or authentication errors.
Resolutions:
- Ensure the API key credential is correctly set up and has sufficient permissions.
- Validate the email format before running the node.
- Check network connectivity and API endpoint availability.
- Enable "Continue On Fail" to handle errors gracefully within workflows.
Links and References
- Omniwallet API Documentation (refer to the official Omniwallet API docs for detailed endpoints and data structures)
- n8n Documentation on Credentials and Error Handling