Qonto icon

Qonto

Interact with Qonto API

Actions45

Overview

The node interacts with the Qonto API to retrieve multiple beneficiary records. It is designed to fetch a list of beneficiaries associated with a Qonto account, supporting filtering and pagination. This node is useful in scenarios where you need to synchronize or analyze beneficiary data from Qonto, such as generating reports, automating payment workflows, or auditing trusted payees.

For example, you can use this node to:

  • Retrieve all validated beneficiaries for reconciliation.
  • Fetch a limited number of pending beneficiaries for review.
  • Filter beneficiaries updated within a specific date range.

Properties

Name Meaning
Authentication Method of authentication; currently supports "API Key".
Return All Whether to return all matching beneficiaries or limit the results.
Limit Maximum number of beneficiaries 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 results:
- Trusted Filter by whether the beneficiary is trusted (true/false).
- Status Filter by status; options are "Pending", "Validated", "Declined".
- IBAN Filter by International Bank Account Number (string match).
- Updated From Minimum update timestamp to filter beneficiaries updated after this date/time.
- Updated To Maximum update timestamp to filter beneficiaries updated before this date/time.

Output

The node outputs an array of JSON objects representing beneficiary records retrieved from the Qonto API. Each object contains details about a beneficiary, such as their status, trust level, IBAN, and timestamps of updates.

If binary data were involved (not indicated here), it would be summarized accordingly, but this node focuses on JSON data output.

Dependencies

  • Requires access to the Qonto API.
  • Needs an API key credential configured in n8n for authentication.
  • The base URL depends on the environment (sandbox or production).
  • No additional external dependencies beyond the Qonto API and proper credentials.

Troubleshooting

  • Common issues:

    • Invalid or missing API key will cause authentication failures.
    • Requesting pages beyond available data may return empty results.
    • Exceeding the maximum limit (over 100) will likely result in errors or truncated responses.
    • Incorrect date formats in filters might cause request rejections.
  • Error messages:

    • "Unknown resource: beneficiary": Indicates the resource parameter was not set correctly.
    • API errors related to authentication or rate limits should be resolved by verifying credentials and usage quotas.
    • If the node returns { json: { error: "..." } } objects, check the error message for specifics and adjust parameters accordingly.

Links and References

Discussion