Digital Wallet Cards icon

Digital Wallet Cards

Interact with Digital Wallet Cards loyalty program API
Join our community

Actions47

Overview

The "Get Operations List" operation under the Analytics resource retrieves a list of all card-related operations (transactions) from the Digital Wallet Cards loyalty program API. This node is useful for analyzing transaction history, auditing card activities, or generating reports on card usage.

Typical use cases include:

  • Fetching detailed transaction logs for specific cards or customers.
  • Filtering operations by type (e.g., accrual, deduction, transfer, expiration).
  • Applying date and amount range filters to analyze transactions within certain periods or amounts.
  • Sorting and paginating large datasets of operations for manageable processing.

For example, a business could use this node to extract all point accruals and deductions for a customer over the last month to reconcile loyalty rewards.

Properties

Name Meaning
Return All Whether to return all results or limit to a specific number. If true, all matching operations are fetched; if false, results are limited by the "Limit" property.
Limit Maximum number of results to return when "Return All" is false. Accepts values between 1 and 1000.
Additional Fields A collection of optional filters and parameters:
- Page: Page number for pagination (default 1).
- Sort By: Field name to sort results by.
- Sort Order: Ascending or Descending (default Descending).
- Filter by Card ID: Filter operations for a specific card.
- Filter by Customer ID: Filter operations for a specific customer.
- Filter by Type: Operation types including Accrual, Deduction, Transfer, Expiration.
- Date From: Start date/time filter.
- Date To: End date/time filter.
- Minimum Amount: Minimum transaction amount filter.
- Maximum Amount: Maximum transaction amount filter.

Output

The output is an array of JSON objects representing individual operations (transactions) matching the query criteria. Each operation object typically includes fields such as:

  • Operation identifiers (e.g., operation ID)
  • Associated card ID and customer ID
  • Operation type (accrual, deduction, transfer, expiration)
  • Transaction amount
  • Date/time of the operation
  • Other metadata related to the transaction

This structured data can be used downstream in workflows for reporting, analytics, or triggering further actions based on transaction details.

The node does not output binary data.

Dependencies

  • Requires an API key credential configured in n8n to authenticate requests against the Digital Wallet Cards API.
  • The node makes HTTP GET requests to the /api/v2/operations endpoint of the Digital Wallet Cards API.
  • Pagination and sorting are handled via query parameters supported by the API.

Troubleshooting

  • Common issues:

    • Missing or invalid API credentials will cause authentication errors.
    • Providing invalid filter values (e.g., incorrect date formats or unsupported operation types) may result in API errors.
    • Requesting too many records without enabling "Return All" may truncate results unexpectedly.

  • Error messages:

    • "Unknown analytics operation: getOperationsList": Indicates the operation parameter was not set correctly.
    • Validation errors if required fields are missing or malformed.
    • API rate limits or network errors may cause request failures.

  • Resolutions:

    • Ensure API credentials are properly set up and valid.
    • Validate input parameters before execution.
    • Use "Return All" cautiously with large datasets to avoid performance issues.
    • Check API documentation for correct filter values and formats.

Links and References

Discussion