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
The node interacts with the bunq banking API to list transactions for a specified monetary account. It allows users to retrieve transaction data filtered by date range and amount, with options to limit the number of results or return all available transactions. This is useful for financial reporting, auditing, or integrating transaction data into other workflows.
Practical examples:
- Fetching all transactions from a specific bank account within the last month.
- Retrieving up to 100 recent transactions above a certain amount for expense tracking.
- Automating reconciliation processes by listing transactions filtered by date and amount criteria.
Properties
| Name | Meaning |
|---|---|
| User ID | The ID of the user. Leave empty to use the current authenticated user. |
| Account ID | The ID of the monetary account to list transactions from. (Required) |
| Return All | Whether to return all matching transactions or only up to a given limit. |
| Limit | Maximum number of transactions to return if "Return All" is false. Range: 1 to 200. |
| Additional Fields | Optional filters to narrow down the transactions: |
| - From Date | Filter transactions from this date (inclusive). |
| - To Date | Filter transactions until this date (inclusive). |
| - Min Amount | Filter transactions with an amount greater than or equal to this value. |
| - Max Amount | Filter transactions with an amount less than or equal to this value. |
Output
The output is a JSON array where each item represents a transaction object returned by the bunq API. Each transaction includes details such as amounts, dates, descriptions, and related metadata formatted consistently by the node.
No binary data output is produced by this operation.
Dependencies
- Requires access to the bunq banking API via configured credentials that provide necessary authentication tokens or API keys.
- The node uses internal helper functions to make HTTP requests to the bunq API and format responses.
Troubleshooting
- Missing or invalid Account ID: The "Account ID" property is required. Ensure it is provided and correct.
- API authentication errors: Verify that the API credentials are correctly set up and have sufficient permissions.
- Date filter format issues: Dates must be valid ISO date/time values; otherwise, the API may reject the request.
- Limit out of range: The "Limit" property must be between 1 and 200 when "Return All" is false.
- Empty results: If no transactions match the filters, the output will be an empty array.
- Network or API errors: These will throw exceptions unless "Continue On Fail" is enabled, in which case error messages are included in the output.