Actions46
- Attachment Actions
- Attachments in a Transaction Actions
- Beneficiary Actions
- Card Actions
- Client Actions
- Client Invoice Actions
- Credit Note Actions
- External Transfer Actions
- Insurance Contract Actions
- Internal Transaction Actions
- Label Actions
- Membership Actions
- Organization Actions
- Request Actions
- Statement Actions
- Supplier Invoice Actions
- Team Actions
- Transaction Actions
Overview
This node interacts with the Qonto API to list bank transactions for a specified bank account identified by its IBAN. It allows users to retrieve transaction data filtered by various criteria such as status, date ranges (updated, emitted, settled), transaction side (credit or debit), operation type, and presence of attachments or labels. This is useful for financial reporting, reconciliation, auditing, or monitoring cash flow within an organization.
Practical examples include:
- Fetching all completed credit transactions for a specific bank account in a given date range.
- Retrieving only transactions that have attachments or labels embedded for detailed review.
- Limiting the number of transactions returned for quick summaries or dashboards.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with the Qonto API. Options: "Login and Secret-Key" or "OAuth2". |
| Return All | Whether to return all matching transactions or limit the results. Boolean value. |
| Limit | Maximum number of transactions to return if "Return All" is false. Minimum value is 1. Default is 50. |
| Iban | The IBAN of the bank account for which to retrieve transactions. Required string input. |
| Filters | Collection of optional filters to narrow down the transactions: |
| - Status | Filter by transaction status. Allowed values: "pending", "declined", "completed". Only one can be used at a time. |
| - Updated_at_from / Updated_at_to | Date-time range filter for when transactions were last updated. |
| - Emitted_at_from / Emitted_at_to | Date-time range filter for when transactions were emitted. |
| - Settled_at_from / Settled_at_to | Date-time range filter for when transactions were settled. |
| - Side | Filter by transaction side: "Credit" or "Debit". |
| - Operation Type | Filter by operation type such as "card", "transfer", or "income". Only one can be used at a time. |
| - With_attachments | Boolean flag to filter transactions based on whether they have one or more attachments. |
| - Labels | Boolean flag to embed labels in each transaction's response object. |
| - Attachments | Boolean flag to embed attachments in each transaction's response object. |
Output
The node outputs an array of transaction objects in the json output field. Each transaction object contains details about individual transactions retrieved from the Qonto API according to the specified filters and parameters.
If the user requests labels or attachments to be included, these will be embedded within each transaction object accordingly.
No binary data output is produced by this operation.
Dependencies
- Requires access to the Qonto API.
- Requires either an API key credential ("Login and Secret-Key") or OAuth2 authentication configured in n8n.
- The node uses helper functions to handle API requests and pagination internally.
Troubleshooting
Common issues:
- Invalid or missing IBAN parameter will cause the request to fail.
- Using incompatible filter combinations (e.g., multiple statuses) may not work as expected since only single values are supported for some filters.
- Exceeding rate limits imposed by the Qonto API could result in errors or throttling.
- Incorrect authentication setup will lead to authorization errors.
Error messages:
- Authorization errors indicate invalid or missing credentials; verify API keys or OAuth2 tokens.
- Validation errors often relate to incorrect filter formats or missing required fields like IBAN.
- Network or timeout errors suggest connectivity issues; retry or check network settings.