Digital Wallet Cards icon

Digital Wallet Cards

Interact with Digital Wallet Cards loyalty program API
Join our community

Actions47

Overview

The node interacts with a Digital Wallet Cards loyalty program API, specifically focusing on communication-related operations. For the Communication resource and the Get Push Notifications operation, it retrieves the history of push notifications sent to cardholders. This is useful for auditing, monitoring notification delivery, or analyzing user engagement with push messages.

Typical use cases include:

  • Fetching all push notifications sent within a certain date range.
  • Filtering notifications by card ID, customer ID, type (e.g., balance update, promotion), or sent status.
  • Paginating through large sets of push notification records.
  • Sorting notifications by specific fields in ascending or descending order.

For example, a marketing team might use this node to pull all promotional push notifications sent last month to evaluate campaign effectiveness.

Properties

Name Meaning
Return All Whether to return all results or limit to a specific number. If true, fetches all available push notifications matching the filters; if false, limits the number of results returned.
Limit Maximum number of results to return when "Return All" is false. Accepts values from 1 to 1000.
Additional Fields A collection of optional filters and parameters:
- Page: Page number for pagination.
- Sort By: Field name to sort the results by.
- Sort Order: Ascending or Descending.
- Filter by Card ID: Filter notifications for a specific card.
- Filter by Customer ID: Filter notifications for a specific customer.
- Filter by Type: Filter by notification type: Balance Update, Tier Change, Expiration Warning, Promotion.
- Filter by Sent Status: Boolean to filter by whether the notification was sent.
- Date From: Start date/time to filter notifications.
- Date To: End date/time to filter notifications.

Output

The output is an array of JSON objects representing push notification records. Each record typically includes details such as:

  • Notification ID
  • Card ID and/or Customer ID associated with the notification
  • Type of notification (e.g., balance update, promotion)
  • Title and message content
  • Sent status and timestamps
  • Other metadata related to the push notification

If multiple items are returned, they are aggregated into a single array output.

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.
  • Pagination and sorting utilities are used internally to handle large result sets efficiently.

Troubleshooting

  • Common issues:

    • Providing invalid or missing required parameters like cardId or customerId in filters may result in empty responses or errors.
    • Exceeding API rate limits could cause request failures.
    • Incorrect date formats in "Date From" or "Date To" fields may lead to API errors.

  • Error messages:

    • "Unknown communication operation: getPushNotifications": Indicates the operation name is incorrect or unsupported.
    • Validation errors if required fields are missing.
    • Network or authentication errors if API credentials are misconfigured.

  • Resolutions:

    • Ensure all required parameters are correctly set.
    • Use valid ISO 8601 date-time strings for date filters.
    • Verify API credentials and permissions.
    • Use "Return All" carefully to avoid fetching excessively large datasets.

Links and References

This summary covers the static analysis of the node's execute method for the Communication resource's Get Push Notifications operation, including input properties, output structure, dependencies, and troubleshooting tips.

Discussion