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
The node interacts with a Digital Wallet Cards loyalty program API, specifically managing operations related to loyalty cards. The "Add Stamps" operation allows users to add a specified number of stamps to a particular card. This is useful in scenarios where businesses use stamp-based loyalty programs (e.g., coffee shops giving a stamp per purchase) and want to automate the process of updating customers' cards.
Practical examples:
- Adding 5 stamps to a customer's loyalty card after they make a qualifying purchase.
- Recording a transaction with an optional description and transaction ID for audit or tracking purposes.
Properties
| Name | Meaning |
|---|---|
| Amount | The number of stamps to add to the card (must be a non-negative number, precision 2). |
| Description | Optional text describing the reason or details of the stamp addition operation. |
| Transaction ID | Optional unique identifier for the transaction; if not provided, one is generated automatically. |
Output
The output JSON contains the response from the API after adding stamps to the card. It typically includes updated card information reflecting the new stamp count and transaction details confirming the operation's success.
The node does not output binary data for this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Digital Wallet Cards API.
- The node uses HTTP methods (POST) to communicate with the endpoint
/api/v2/cards/{cardId}/add-stamp. - No additional external dependencies are required beyond the configured API credentials.
Troubleshooting
- Missing Required Fields: If
cardIdoramountis missing or invalid, the node will throw an error indicating these fields are required. - Invalid Amount: Providing a negative amount or non-numeric value will cause validation errors.
- API Errors: Network issues or invalid API credentials can result in failed requests. Ensure the API key is valid and the service is reachable.
- Transaction ID Conflicts: If a duplicate transaction ID is used, the API might reject the request. Either omit it to auto-generate or ensure uniqueness.
- Empty Description: This field is optional; leaving it empty should not cause errors.
Links and References
- Digital Wallet Cards API Documentation (hypothetical link as actual URL is not provided)
- n8n documentation on Creating Custom Nodes
- General info on Loyalty Programs
If you need summaries for other operations or resources, feel free to ask!