Qonto

Overview

This node interacts with the Qonto API to list external transfers associated with a user's account. It allows users to retrieve detailed information about external transfers, optionally filtered by various criteria such as scheduled date range, status, update timestamps, and beneficiary IDs.

Common scenarios where this node is beneficial include:

• Financial reporting or reconciliation workflows that require fetching recent or historical external transfer data.
• Automating monitoring of payment statuses (e.g., pending, settled) for accounting or auditing purposes.
• Integrating Qonto external transfer data into other systems like CRMs, ERPs, or dashboards.

For example, a user can configure the node to fetch all external transfers scheduled within a specific date range and with a "settled" status to generate a report of completed payments.

Properties

Name	Meaning
Authentication	Method of authenticating with the Qonto API. Options: "Login and Secret-Key" or "OAuth2".
Return All	Boolean flag indicating whether to return all matching results or limit the number of results returned.
Limit	Maximum number of results to return when "Return All" is false. Minimum value is 1. Default is 50.
Filters	Collection of optional filters to narrow down the list of external transfers: - Scheduled_date_from: Start date/time for scheduled transfers. - Scheduled_date_to: End date/time for scheduled transfers. - Status: Filter by transfer status; allowed values are pending, processing, canceled, declined, settled (only one status at a time). - Updated_at_from: Start date/time for last update. - Updated_at_to: End date/time for last update. - Beneficiary_ids: Comma-separated list of beneficiary IDs to filter transfers by beneficiaries.

Output

The node outputs an array of JSON objects representing external transfers retrieved from the Qonto API. Each object contains details about an external transfer, such as identifiers, amounts, currency, scheduled dates, status, beneficiary information, and any attachments linked to the transfer.

The exact structure depends on the Qonto API response but typically includes fields like:

• id: Unique identifier of the external transfer.
• amount: Transfer amount.
• currency: Currency code.
• scheduled_date: Date the transfer is scheduled for.
• status: Current status of the transfer.
• beneficiary_id: Identifier of the beneficiary.
• Other metadata related to the transfer.

No binary data output is produced by this operation.

Dependencies

• Requires valid authentication credentials for the Qonto API, either via login and secret key or OAuth2 token.
• The node uses internal helper functions to make HTTP requests to the Qonto API endpoints.
• No additional external dependencies beyond standard n8n environment and the Qonto API access.

Troubleshooting

• Authentication errors: Ensure that the provided API credentials or OAuth2 tokens are valid and have sufficient permissions to access external transfer data.
• Empty results: If no transfers are returned, verify that the filter parameters (dates, status, beneficiary IDs) are correct and that there are matching records in the Qonto account.
• Invalid filter values: Status filter only accepts one of the specified values (pending, processing, canceled, declined, settled). Using unsupported values will likely cause errors or empty responses.
• API rate limits: If many requests are made in a short period, the Qonto API may throttle requests. Implement retry logic or reduce request frequency if encountering rate limit errors.
• Limit vs Return All: When "Return All" is false, ensure the "Limit" property is set appropriately to avoid missing data.

Links and References

• Qonto API Documentation — Official API docs for understanding external transfer endpoints and data structures.
• n8n Documentation — For general guidance on using and configuring nodes in n8n workflows.