Qonto icon

Qonto

Interact with Qonto API
Join our community

Actions45

Overview

The node interacts with the Qonto API to retrieve multiple bank statements based on user-defined filters and pagination options. It is designed to fetch a list of statements from Qonto accounts, which can be useful for financial reporting, reconciliation, or auditing purposes.

Typical use cases include:

  • Downloading all bank statements within a specific date range.
  • Retrieving statements for particular bank accounts or IBANs.
  • Paginating through large sets of statements when not returning all at once.

For example, a user might configure this node to get all statements from January 1st to March 31st for certain bank accounts to generate a quarterly financial report.

Properties

Name Meaning
Authentication Method of authenticating with Qonto API. Only option: "API Key".
Return All Whether to return all matching statements or limit the number of results returned.
Limit Maximum number of statements to return if not returning all (default 100, max 100).
Page Page number to retrieve when limiting results (starts at 1).
Filters Collection of optional filters to narrow down the statements retrieved:
- Bank Account IDs Comma-separated list of bank account IDs to filter statements by specific accounts.
- IBANs Comma-separated list of IBANs to filter statements by specific international bank numbers.
- Period From Start date/time to filter statements from this date onwards.
- Period To End date/time to filter statements up to this date.

Output

The node outputs an array of JSON objects representing bank statements retrieved from Qonto. Each object contains details about a single statement, such as its ID, associated bank account, period covered, and other metadata provided by the Qonto API.

If binary data were involved (e.g., PDF files of statements), it would be included in the binary output field, but this node focuses on JSON data only.

Dependencies

  • Requires an API key credential for authenticating requests to the Qonto API.
  • The node uses the Qonto API base URL, switching between sandbox and production environments based on credentials configuration.
  • No additional external dependencies beyond the Qonto API and n8n's HTTP request capabilities.

Troubleshooting

  • Common issues:

    • Invalid or missing API key will cause authentication failures.
    • Requesting pages beyond available data may return empty results.
    • Using invalid date formats in filters may cause errors or no results.
    • Exceeding the maximum limit (over 100) will be rejected.

  • Error messages:

    • "Unknown resource: statement" — indicates the resource parameter was set incorrectly; ensure "Statement" is selected.
    • API errors related to authentication or rate limits will be passed through; verify API key validity and usage quotas.
    • If continueOnFail is enabled, errors per item are returned inside the JSON under an error property.

Links and References

Discussion