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 integrates with the Qonto API to list financial statements for a specified organization. It is useful for retrieving bank statement data within a given date range, enabling users to automate financial reporting, reconciliation, or auditing workflows. For example, a business could use this node to fetch monthly statements automatically and process them further in their accounting system.
Properties
Name | Meaning |
---|---|
Authentication | Method of authentication to use: "Login and Secret-Key" or "OAuth2". |
Organization ID | The unique identifier of the organization whose statements are to be listed (required). |
Start Date | Optional filter to fetch statements created after this date. |
End Date | Optional filter to fetch statements created before this date. |
Output
The node outputs an array of JSON objects representing the statements retrieved from the Qonto API. Each object contains details about a statement such as its metadata and content as provided by the API. The output does not include binary data.
Dependencies
- Requires access to the Qonto API.
- Requires either an API key credential ("Login and Secret-Key") or OAuth2 credentials configured in n8n.
- Uses helper functions (
qontoApiRequest
andhandleListing
) to make authenticated HTTP requests and handle pagination.
Troubleshooting
- Missing or invalid Organization ID: The node requires a valid organization ID; ensure it is correctly set.
- Authentication errors: Verify that the chosen authentication method is properly configured and the credentials are valid.
- Date filters format: Ensure that start and end dates are in the correct ISO datetime format.
- API rate limits or connectivity issues: Network problems or API limits may cause failures; check API status and retry policies.
- Empty results: If no statements are returned, verify the date range and organization ID filters.