Actions47
- Template Actions
- Communication Actions
- Card Actions
- Create
- Get
- Get All
- Update
- Delete
- Get Balance
- Add Points
- Deduct Points
- Add Amount
- Deduct Amount
- Add Stamps
- Deduct Stamps
- Transfer Points
- Transfer Amount
- Block Card
- Unblock Card
- Generate QR Code
- Get Operations
- Add Visits
- Deduct Visits
- Add Reward
- Deduct Reward
- Receive Reward
- Redeem Coupon
- Set Expiration Date
- Set Membership Tier
- Customer Actions
- Company Actions
- Analytics Actions
- System Actions
Overview
This node interacts with a Digital Wallet Cards loyalty program API, specifically managing customers, cards, companies, templates, communications, analytics, and system operations. For the Customer - Delete operation, it deletes a customer record identified by a unique Customer ID.
Typical use cases include:
- Removing a customer from the loyalty program database when they unsubscribe or request data deletion.
- Cleaning up test or duplicate customer records.
- Automating customer lifecycle management workflows.
Example: Deleting a customer with ID customer_12345 to remove their profile and associated loyalty data from the system.
Properties
| Name | Meaning |
|---|---|
| Customer ID | The unique identifier of the customer to delete. This is required to specify which customer record should be removed. |
Output
The output JSON contains a confirmation of the deletion operation. It typically includes:
success: A boolean indicating if the deletion was successful (usuallytrue).customerId: The ID of the customer that was deleted.
Example output JSON:
{
"success": true,
"customerId": "customer_12345"
}
No binary data is involved in this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Digital Wallet Cards API.
- The base URL for API requests is
https://api.digitalwallet.cards. - The node uses HTTP DELETE method on endpoint
/api/v2/customers/{customerId}to perform the deletion. - Proper permissions and API access must be configured in n8n credentials for this node to work.
Troubleshooting
- Missing Customer ID: If the Customer ID is not provided or invalid, the node will throw an error indicating the missing required field.
- API Authentication Errors: Ensure the API key credential is correctly set up and has permission to delete customers.
- Customer Not Found: If the specified Customer ID does not exist, the API may return a 404 error or similar; handle this gracefully in your workflow.
- Network Issues: Connectivity problems can cause request failures; verify network access to the API endpoint.
- Continue On Fail: If enabled, errors will be returned as part of the output JSON with an error flag and message instead of stopping execution.
Links and References
- Digital Wallet Cards API Documentation (hypothetical link based on base URL)
- n8n Documentation on Creating Custom Nodes
- General REST API best practices for DELETE operations
This summary focuses exclusively on the Customer - Delete operation as requested, extracted from the provided source code and property definitions.