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 "Get All" operation for the "Card" resource in this node retrieves multiple loyalty cards from the Digital Wallet Cards API. It supports fetching either all available cards or a limited subset with pagination and sorting options. This operation is useful when you want to list cards for reporting, analysis, or batch processing within an automation workflow.
Common scenarios:
- Fetching all loyalty cards issued by a company to analyze customer engagement.
- Retrieving a specific number of cards sorted by creation date or other fields.
- Paginating through large sets of cards to process them in batches.
Practical example:
You could use this operation to get all cards created in your loyalty program, sorted by their last update time in descending order, and then send targeted marketing campaigns based on card status or points balance.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all results or limit to a specific number |
| Limit | Maximum number of results to return (used if Return All is false) |
| Additional Fields | Collection of optional parameters: |
| - Page | Page number for pagination (minimum 1) |
| - Sort By | Field name to sort the results by |
| - Sort Order | Sort order direction: "Ascending" or "Descending" |
Output
The output is an array of JSON objects representing the cards retrieved from the API. Each object contains detailed information about a card, such as its unique identifier, associated customer, template, balance, points, stamps, expiration date, status, and metadata.
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 uses the base URL
https://api.digitalwallet.cardsfor API calls. - Pagination and sorting are handled via query parameters sent to the API.
Troubleshooting
- Empty results: If no cards are returned, verify that the account has cards matching the criteria or check if filters (like page or sort) exclude all results.
- Limit exceeded error: The API limits the maximum number of cards per request to 1000. Use pagination (
Pageproperty) to retrieve additional cards. - Invalid sort field: Providing an invalid field name in
Sort Bymay cause API errors. Ensure the field exists in the card schema. - Authentication errors: Ensure the API key credential is correctly set up and has permissions to access card data.
- Malformed JSON in Additional Fields: If using JSON metadata fields elsewhere, ensure valid JSON syntax to avoid parsing errors.
Links and References
- Digital Wallet Cards API Documentation (hypothetical link for reference)
- n8n Documentation on Creating Custom Nodes
- General info on Pagination in APIs