Overview
This node deletes a customer from the Omniwallet API based on the customer's email address. It is useful in scenarios where you need to programmatically remove customer records from your Omniwallet account, such as cleaning up inactive users or complying with data deletion requests.
For example, if you have a list of customer emails that should no longer have access or presence in your system, this node can be used to delete each customer by their email.
Properties
| Name | Meaning |
|---|---|
| Customer Email | The email address of the customer to delete. This must be a valid, non-empty string representing the customer's email. |
Output
The node outputs an array of JSON objects, one per input item, each containing:
success: A boolean indicating whether the deletion was successful.message: A success message when deletion succeeds.email: The email address of the customer targeted for deletion.response: The raw response data returned from the Omniwallet API after the delete request.error: If the operation failed, contains the error message explaining why.itemIndex: The index of the input item related to the output (only present on failure).
No binary data is output by this node.
Dependencies
- Requires an active Omniwallet API credential configured in n8n to authenticate API requests.
- Depends on the external Omniwallet API service being available and reachable.
- Uses a helper function (
omniwalletApiRequest) to make authenticated HTTP DELETE requests to the Omniwallet API.
Troubleshooting
- Empty Email Error: If the "Customer Email" property is empty or only whitespace, the node throws an error stating the email cannot be empty. Ensure the email field is correctly populated.
- API Request Failures: Network issues, invalid credentials, or incorrect API endpoint responses may cause errors. Verify your API key and network connectivity.
- Continue On Fail Behavior: If enabled, the node will continue processing subsequent items even if some deletions fail, returning error details per failed item.
- Encoding Issues: Emails are URL-encoded before sending; ensure emails are valid and properly formatted to avoid encoding problems.
Links and References
- Omniwallet API Documentation (Assumed official API docs for reference)
- n8n Documentation on Creating Custom Nodes