Actions42
- Attachment Actions
- Payment Actions
- Transaction Actions
- Request Inquiry Actions
- Card Actions
- bunq.me Actions
- Webhook Actions
- Scheduled Payment Actions
- Export/Statement Actions
- User Actions
- Monetary Account Actions
Overview
This node interacts with the bunq banking API to manage and retrieve information about bank cards associated with a user. Specifically, the Card - List operation fetches a list of cards for a specified user or the current authenticated user if no user ID is provided. It supports filtering by card type and status, and allows either retrieving all matching cards or limiting the number of results.
Common scenarios where this node is beneficial include:
- Retrieving all active or specific types of cards for auditing or reporting.
- Filtering cards by their status (e.g., lost, stolen) to trigger alerts or follow-up actions.
- Integrating card data into workflows that require up-to-date card information from bunq accounts.
Practical example:
- A finance team wants to generate a report of all VISA cards currently active for a particular user.
- An automated workflow checks for any lost or stolen cards daily and sends notifications to security teams.
Properties
| Name | Meaning |
|---|---|
| User ID | The ID of the user whose cards are to be listed. Leave empty to use the current authenticated user. |
| Return All | Whether to return all matching cards or only up to a specified limit. |
| Limit | Maximum number of cards to return when "Return All" is false. Must be between 1 and 200. |
| Additional Fields | Optional filters to narrow down the list: |
| - Card Type | Filter cards by type. Options: MAESTRO, MASTERCARD, VISA |
| - Status | Filter cards by status. Options: ACTIVE, DEACTIVATED, LOST, STOLEN, EXPIRED |
Output
The output is an array of JSON objects representing cards retrieved from the bunq API. Each object contains detailed information about a card, such as its type, status, and other metadata as returned by the API.
The structure corresponds to the bunq API's card response format, wrapped and normalized by the node's internal formatting function.
No binary data output is produced by this operation.
Dependencies
- Requires access to the bunq banking API.
- Requires valid API credentials configured in n8n for authentication.
- Uses internal helper functions to make HTTP requests to the bunq API and format responses.
Troubleshooting
- Empty results: If no cards are returned, verify the User ID is correct or try leaving it empty to use the current user. Also check filter values for card type and status.
- API errors: Errors from the bunq API (e.g., authentication failures, rate limits) will be thrown. Ensure API credentials are valid and have sufficient permissions.
- Limit issues: When "Return All" is false, ensure the limit is within the allowed range (1-200).
- Network issues: Connectivity problems may cause request failures; verify network access to the bunq API endpoints.