Omniwallet - Get Customer by Email Tool icon

Omniwallet - Get Customer by Email Tool

Retrieve a specific customer by email from Omniwallet API Tool
Join our community

Overview

This node, "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 data into workflows.

For example, if you have a list of customer emails and want to enrich your dataset with their Omniwallet profile information, this node can be used to query each email and return the corresponding customer data.

Properties

Name Meaning
Customer Email The email address of the customer to retrieve from Omniwallet. This must be a valid email string (e.g., "customer@example.com").

Output

The node outputs an array of JSON objects, each representing the customer data retrieved from the Omniwallet API for the given email. The structure of the output JSON corresponds to the data field returned by the API endpoint /customers/{email}.

  • If the request is successful, the output JSON contains the customer's details as provided by Omniwallet.
  • If an error occurs and the node is set to continue on failure, the output JSON will include an error field with the error message, the index of the item that caused the error, and the email queried.

No binary data 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.
  • Proper network access to the Omniwallet API endpoint is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Providing an invalid or incorrectly formatted email may result in a "not found" or similar error from the API.
    • Network connectivity problems can prevent the node from reaching the Omniwallet API.

  • Error messages:

    • Errors returned by the API are captured and included in the output if "Continue On Fail" is enabled.
    • Typical errors might include "Customer not found" or "Unauthorized" due to invalid credentials.

  • Resolution tips:

    • Verify that the API key credential is correctly set up and has the necessary permissions.
    • Ensure the email input is correctly formatted and corresponds to an existing customer.
    • Check network connectivity and firewall settings to allow outbound requests to the Omniwallet API.

Links and References

  • Omniwallet API documentation (refer to the official Omniwallet API docs for details on the /customers/{email} endpoint).
  • n8n documentation on creating and using API credentials.
  • General best practices for handling API errors and retries in n8n workflows.

Discussion