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 provides integration with a Digital Wallet Cards loyalty program API, specifically enabling operations on loyalty cards. The Update Card operation allows users to modify various attributes of an existing card such as its status, balance, points, stamps, expiration date, membership tier, and additional metadata.
This operation is useful in scenarios where you need to maintain or adjust the state of a loyalty card dynamically, for example:
- Updating a card's status from "active" to "blocked" after suspicious activity.
- Adjusting the balance or points after a transaction or promotion.
- Extending the expiration date for loyal customers.
- Changing membership tiers based on customer behavior.
- Adding custom metadata for integration or tracking purposes.
Practical example: A retail business could use this node to update a customer's loyalty card after a purchase, adding points earned and updating the membership tier if they reach a new level.
Properties
| Name | Meaning |
|---|---|
| Card ID | The unique identifier of the card to update. |
| Update Fields | Collection of fields to update on the card. Possible fields include: |
| - Status: Card status; options are Active, Inactive, Blocked, Expired | |
| - Balance: Numeric value representing the card's balance (precision up to 2 decimals) | |
| - Points: Numeric value representing loyalty points on the card | |
| - Stamps: Numeric value representing stamps collected on the card | |
| - Expiration Date: Date/time when the card expires | |
| - Membership Tier: String indicating the membership tier | |
| - Metadata: JSON object containing additional custom data related to the card |
Output
The output is a JSON object representing the updated card details returned by the API after the update operation. It typically includes the updated fields and other card information as confirmed by the backend service.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential configured in n8n to authenticate requests against the Digital Wallet Cards API.
- The node makes HTTP PATCH requests to the
/api/v2/cards/{cardId}endpoint of the Digital Wallet Cards API. - The node depends on utility functions for making API requests, validating required fields, cleaning objects, and transforming API responses.
Troubleshooting
Error: "At least one field must be specified for update"
This error occurs if no update fields are provided. Ensure that at least one property inside "Update Fields" is set before executing the node.Invalid Card ID
If the provided Card ID does not exist or is malformed, the API will return an error. Verify the Card ID is correct and exists in the system.JSON Parsing Errors in Metadata
The "Metadata" field expects valid JSON. Invalid JSON syntax will cause errors. Use proper JSON formatting.API Authentication Failures
Ensure the API key credential is correctly configured and has sufficient permissions to perform update operations.Network or API Endpoint Issues
Confirm network connectivity and that the API base URL (https://api.digitalwallet.cards) is reachable.
Links and References
- Digital Wallet Cards API Documentation (hypothetical link for reference)
- n8n Documentation on Creating Custom Nodes
- JSON Syntax Guide: https://www.json.org/json-en.html