Digital Wallet Cards icon

Digital Wallet Cards

Interact with Digital Wallet Cards loyalty program API

Card → Get Balance

AI-generated

Overview

This node interacts with a Digital Wallet Cards loyalty program API, specifically focusing on operations related to loyalty cards. The "Get Balance" operation retrieves the current balance details of a specified card, including monetary balance, points, stamps, last update timestamp, and expiration date.

Typical use cases include:

  • Checking a customer's loyalty card balance before processing a transaction.
  • Displaying updated loyalty points or stamps in a customer portal.
  • Automating workflows that depend on card balances, such as triggering rewards or notifications when certain thresholds are met.

Example:
You can use this node to fetch the balance of a loyalty card by providing its unique Card ID, then use the returned balance data to decide if a customer qualifies for a discount or reward.

Properties

Name Meaning
Card ID The unique identifier of the card whose balance you want to retrieve.

Output

The output JSON object for the "Get Balance" operation includes:

  • cardId (string): The unique identifier of the card queried.
  • balance (number): The current monetary balance on the card.
  • points (number): The number of loyalty points available on the card.
  • stamps (number): The number of stamps accumulated on the card.
  • lastUpdated (string, ISO 8601 datetime): Timestamp of the last update to the card's balance.
  • expirationDate (string, ISO 8601 datetime or empty): Expiration date of the card, if set.

No binary data is output by this operation.

Dependencies

  • Requires an API key credential configured in n8n to authenticate requests to the Digital Wallet Cards API.
  • The node makes HTTP requests to the base URL https://api.digitalwallet.cards.
  • No additional external dependencies beyond standard HTTP connectivity and authentication.

Troubleshooting

  • Missing or invalid Card ID: The operation requires a valid Card ID. If omitted or incorrect, the node will throw an error indicating the missing required field.
  • API authentication errors: Ensure the API key credential is correctly configured and has sufficient permissions.
  • Network issues: Connectivity problems to the API endpoint may cause request failures.
  • Unexpected API responses: If the API changes or returns unexpected data, the node might fail or return incomplete information.

To resolve errors:

  • Verify the Card ID is correct and exists in the system.
  • Check API credentials and permissions.
  • Confirm network access to the API endpoint.
  • Review error messages returned by the node for specific guidance.

Links and References

Discussion