Qonto icon

Qonto

Consume Qonto API

Actions46

Overview

This node interacts with the Qonto API to list beneficiaries associated with a user's account. It allows users to retrieve a filtered or complete list of beneficiaries, which can be useful for financial management, auditing, or integration with other systems that require beneficiary data.

Common scenarios include:

  • Fetching all beneficiaries linked to an organization for reconciliation.
  • Filtering beneficiaries by IBAN, status, or trust level to focus on specific subsets.
  • Using date filters to get beneficiaries updated within a certain timeframe.

Practical example: A finance team automates monthly reporting by listing all trusted beneficiaries updated in the last month to verify payment recipients.

Properties

Name Meaning
Authentication Method of authentication to use when connecting to the Qonto API. Options: "Login and Secret-Key" or "OAuth2".
Return All Boolean flag indicating whether to return all beneficiaries or limit the number of results.
Limit Maximum number of beneficiaries to return if "Return All" is false. Minimum value is 1. Default is 50.
Filters Collection of optional filters to narrow down the list of beneficiaries:
- IBAN: Filter by one or more IBANs.
- Trusted: Filter by boolean trust status (true/false).
- Status: Filter by beneficiary status; possible values are "pending", "validated", and "declined".
- Updated_at_from: Start datetime to filter beneficiaries updated after this timestamp.
- Updated_at_to: End datetime to filter beneficiaries updated before this timestamp.

Output

The node outputs an array of beneficiary objects in the json field. Each object represents a beneficiary with details as returned by the Qonto API, such as identifiers, IBAN, status, trust flag, and timestamps.

If multiple beneficiaries are returned, they are output as an array of JSON objects.

No binary data output is involved in this operation.

Dependencies

  • Requires access to the Qonto API.
  • Requires user credentials configured in n8n either via an API key credential or OAuth2 authentication.
  • The node uses helper functions to handle API requests and pagination internally.

Troubleshooting

  • Empty Results: If no beneficiaries are returned, check the applied filters for correctness and ensure the account has beneficiaries matching those criteria.
  • Authentication Errors: Ensure that the provided authentication method and credentials are valid and have sufficient permissions.
  • API Rate Limits: If many requests are made in a short time, the Qonto API may throttle requests. Implement retry logic or reduce request frequency.
  • Invalid Filter Values: Passing unsupported status values or malformed dates may cause errors. Use only documented filter options and ISO 8601 date formats.

Links and References

Discussion