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 "Unblock Card" operation allows users to unblock a previously blocked card, restoring its active status and enabling it for transactions again.
This node is beneficial in scenarios where a cardholder's card was blocked (e.g., due to suspected fraud or loss) and needs to be reactivated without issuing a new card. For example, a retail loyalty program administrator can unblock a customer's card after verifying their identity, allowing the customer to resume earning and redeeming points.
Properties
| Name | Meaning |
|---|---|
| Card ID | The unique identifier of the card to unblock (e.g., card_12345...). This is required. |
Output
The output JSON contains the response from the API after unblocking the card. It typically includes details about the card's updated status and other relevant card information as returned by the API. The exact structure depends on the API response but generally confirms the success of the unblock operation and provides the current state of the card.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential configured in n8n to authenticate requests to the Digital Wallet Cards API.
- The base URL for API requests is
https://api.digitalwallet.cards. - The node uses internal utility functions for making HTTP requests, validating fields, and transforming responses.
Troubleshooting
- Missing Card ID: If the "Card ID" property is not provided or invalid, the node will throw an error indicating that the card identifier is required.
- API Errors: Errors returned by the API (e.g., card not found, card not blocked) will be propagated. Check the error message for details.
- Network Issues: Connectivity problems may cause request failures; ensure network access to the API endpoint.
- Permission Issues: Ensure the API key has sufficient permissions to perform unblock operations.
- JSON Parsing Errors: If additional metadata fields are used elsewhere, ensure they are valid JSON strings.
Links and References
- Digital Wallet Cards API Documentation (hypothetical link based on base URL)
- n8n Documentation on Creating Custom Nodes