Actions45
- Attachment Actions
- Beneficiary Actions
- Business Account Actions
- Card Actions
- Client Actions
- Client Invoice Actions
- Credit Note Actions
- External Transfer Actions
- Insurance Contract Actions
- Internal Transfer Actions
- Label Actions
- Membership Actions
- Organization Actions
- Quote Actions
- Request Actions
- SEPA Transfer Actions
- Statement Actions
- Supplier Invoice Actions
- Team Actions
- Transaction Actions
Overview
The node interacts with the Qonto API to retrieve multiple transactions associated with a specified bank account. It is designed to fetch transaction data in bulk, supporting pagination, filtering by status and date range, and sorting by creation date. This node is useful for financial reporting, reconciliation, or auditing workflows where users need to analyze or process batches of transaction records from their Qonto bank accounts.
Practical examples include:
- Fetching all completed transactions within a specific date range for accounting purposes.
- Retrieving pending transactions to monitor cash flow.
- Exporting a limited number of recent transactions sorted by creation date for review.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication; currently supports "API Key". |
| Bank Account | The specific bank account to retrieve transactions for. Options are dynamically loaded from available accounts. |
| Return All | Whether to return all matching transactions or limit the results. |
| Limit | Maximum number of transactions to return when not returning all (default 100, max 100). |
| Page | Page number to retrieve when limiting results (starts at 1). |
| Filters | Collection of filters to narrow down transactions: |
| - Status | Filter transactions by status: Completed, Pending, or Declined. |
| - Date From | Start date to filter transactions from. |
| - Date To | End date to filter transactions up to. |
| Options | Additional options for the query: |
| - Sort By | Sort transactions by creation date ascending or descending (default descending). |
Output
The node outputs an array of JSON objects representing transactions retrieved from the Qonto API. Each object contains detailed transaction data such as amounts, dates, statuses, and related metadata.
If binary data were involved (not indicated here), it would be summarized accordingly, but this node focuses on JSON transaction data only.
Dependencies
- Requires an API key credential for authenticating requests to the Qonto API.
- The node uses the Qonto API endpoints, switching between sandbox and production environments based on configuration.
- Dynamic loading of bank accounts requires connectivity to the Qonto service.
Troubleshooting
Common issues:
- Invalid or missing API key will cause authentication failures.
- Selecting a bank account that does not exist or has no transactions may return empty results.
- Requesting pages beyond available data returns empty arrays.
- Exceeding the maximum limit (over 100) will likely result in validation errors.
Error messages:
"Unknown resource: transaction"— indicates the resource parameter was incorrectly set or missing.- API errors related to authentication or permissions should be resolved by verifying the API key and its access rights.
- Network timeouts or connectivity issues can cause request failures; ensure stable internet connection and correct endpoint configuration.