Digital Wallet CardsInstall

Overview

This node interacts with a Digital Wallet Cards loyalty program API, specifically focusing on operations related to loyalty cards. The "Get Operations" operation under the "Card" resource is intended to retrieve the transaction history or operations performed on a specific card.

However, for the "Get Operations" operation, the node does not directly fetch data from an endpoint. Instead, it returns a message indicating that this endpoint is not directly available and suggests using the analytics resource's operations list instead. This means users looking to get detailed transaction histories should use the analytics operations list rather than this direct card operation.

Common scenarios where this node is beneficial:

• Managing loyalty cards by creating, updating, or deleting them.
• Retrieving card details and balances.
• Adding or deducting points, amounts, stamps, visits, rewards, or redeeming coupons on cards.
• Blocking or unblocking cards.
• Generating QR codes for cards.
• Accessing transaction history (via analytics operations list as recommended).

Practical example:

If you want to get the transaction history of a card, you might try the "Get Operations" operation on the card resource. However, this node will inform you that the direct endpoint is unavailable and recommend using the analytics resource's operations list instead, guiding you to the correct approach.

Properties

Output

The output is a JSON array containing one or more objects depending on the operation performed. For the "Get Operations" operation on the Card resource, the output is a JSON object with the following structure:

{
  "cardId": "string",
  "message": "Operations endpoint not directly available - use analytics operations list instead"
}

This indicates that no actual operations data is returned here; instead, it's an informational message.

For other card operations (not requested here), the output typically contains detailed card information or confirmation of the performed action.

The node does not output binary data.

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.
• Uses internal utility functions for making HTTP requests, pagination, validation, and response transformation.

Troubleshooting

• Issue: Using "Get Operations" on the Card resource returns only an informational message, not actual transaction data.

  • Cause: The direct endpoint for card operations history is not implemented in this resource.
  • Resolution: Use the Analytics resource with the "Get Operations List" operation to retrieve transaction history.

• Issue: Missing required "Card ID" parameter.

  • Cause: The operation requires a valid card identifier.
  • Resolution: Ensure the "Card ID" property is set correctly before executing the node.

• Issue: Errors related to invalid or missing API credentials.

  • Cause: The node requires a valid API authentication token.
  • Resolution: Configure the API key credential properly in n8n.

• Issue: Empty or unexpected responses.

  • Cause: Could be due to incorrect parameters or API limitations.
  • Resolution: Verify input parameters and consult API documentation for limits and filters.

Links and References

• Digital Wallet Cards API Documentation (hypothetical link based on base URL)
• For transaction history, refer to the Analytics resource's "Get Operations List" operation within this node's capabilities.