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 "Card" resources. The Get Card operation retrieves detailed information about a specific loyalty card using its unique identifier.
This node is useful in scenarios where you need to fetch the current state or details of a loyalty card, such as checking card status, balance, points, stamps, expiration date, and other metadata. For example, it can be used in customer service workflows to verify a customer's card details or in automated marketing campaigns to personalize offers based on card data.
Properties
| Name | Meaning |
|---|---|
| Card ID | The unique identifier of the card to retrieve. Example format: card_12345... |
Output
The output JSON contains the full details of the requested card as returned by the API. This typically includes fields such as:
- Card ID
- Status (e.g., active, blocked)
- Balance amount
- Points accumulated
- Stamps count
- Expiration date
- Membership tier
- Metadata (additional custom data)
The exact structure depends on the API response but generally represents all relevant card attributes.
The node does not output binary data for 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 standard HTTP methods (GET) to interact with the API endpoints.
Troubleshooting
- Missing Card ID: If the "Card ID" property is empty or invalid, the node will throw an error indicating that the card ID is required.
- Card Not Found: If the specified card ID does not exist, the API may return a 404 error or similar. Ensure the card ID is correct.
- Authentication Errors: If the API key credential is missing or invalid, authentication errors will occur. Verify the API key configuration.
- API Rate Limits: Excessive requests might lead to rate limiting by the API. Implement retries or delays if needed.
- JSON Parsing Errors: If additional metadata fields are provided in JSON format elsewhere, ensure they are valid JSON strings to avoid parsing errors.
Links and References
- Digital Wallet Cards API Documentation (hypothetical link, replace with actual if available)
- n8n Documentation on Creating Custom Nodes
- General REST API usage best practices
If you want me to analyze other operations or resources, just let me know!