Overview
This node deletes a customer from the Omniwallet system by using the customer's email address. It is useful in scenarios where you need to programmatically remove customer records from Omniwallet, such as cleaning up inactive users, handling account deletions, or automating customer management workflows.
For example, if you have a list of customer emails that should no longer have access to your services, this node can be used to delete those customers from Omniwallet automatically.
Properties
| Name | Meaning |
|---|---|
| Customer Email | Email of the customer to delete |
Output
The node outputs an array of JSON objects, each corresponding to one deletion attempt. Each output item contains:
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 upon successful deletion.error: If the deletion fails, this field contains the error message.itemIndex: The index of the input item that caused the error (only present on failure).
No binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the Omniwallet API.
- The node uses an internal helper function to make HTTP DELETE requests to the Omniwallet API endpoint
/customers/{email}.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing an incorrect or non-existent customer email will result in an error from the API.
- Network connectivity problems may prevent the node from reaching the Omniwallet API.
Error messages:
- Errors returned from the API are captured and included in the output under the
errorfield. - If "Continue On Fail" is disabled, the node execution will stop on the first error encountered.
- To handle errors gracefully, enable "Continue On Fail" so that the node processes all inputs and reports individual failures.
- Errors returned from the API are captured and included in the output under the
Links and References
- Omniwallet API documentation (refer to the official Omniwallet API docs for details on customer deletion endpoints).