Qonto icon

Qonto

Consume Qonto API

Actions46

Overview

This node integrates with the Qonto API to create external bank transfers using creditor data. It allows users to initiate payments from a debit IBAN account to a credit IBAN account, specifying details such as the creditor's name, currency, amount, and optional attachments or scheduling information.

Common scenarios for this node include automating vendor payments, payroll disbursements, or any business process requiring scheduled or immediate external bank transfers with detailed creditor information.

For example, a finance team can use this node to programmatically send payments to suppliers by providing the supplier’s IBAN, name, and payment amount, optionally attaching invoices or payment references.

Properties

Name Meaning
Authentication Method of authentication to use: either "Login and Secret-Key" or "OAuth2".
Debit IBAN The IBAN of the bank account from which the money will be debited. This is required.
Credit IBAN The IBAN of the creditor’s bank account to which the money will be credited. This is required.
Credit Account Name The name of the credit account holder (creditor). This is required.
Credit Account Currency The currency of the credit account. Currently, only "EUR" is supported. This is required.
Reference A text reference describing the transfer, up to 140 characters. Optional but useful for clarifying the purpose of the transfer.
Note Additional notes related to the transfer. Optional.
Currency The currency of the transfer amount. Must be "EUR". This is required.
Scheduled Date The date when the transfer is scheduled to be sent, formatted as YYYY-MM-DD. Optional; if omitted, the transfer may be immediate.
Amount The amount of money to transfer, in the specified currency. This is required.
Idempotency Key A unique key to ensure idempotency of the request, preventing duplicate transfers if the request is retried. Optional; if not provided, a UUID is generated automatically.
Attachment IDs An array of binary attachments to add to the transfer, such as invoices or receipts. Multiple files can be specified by their binary property names. Optional.

Output

The node outputs JSON data representing the created external transfer as returned by the Qonto API. This typically includes details such as:

  • Transfer ID
  • Status of the transfer
  • Debit and credit account details
  • Amount and currency
  • Scheduled date
  • Any attached documents or metadata

If multiple items are processed, the output is an array of such objects.

The node does not output binary data directly for this operation.

Dependencies

  • Requires access to the Qonto API.
  • Requires user credentials configured in n8n, either via an API key credential or OAuth2 authentication.
  • Uses the uuid library internally to generate idempotency keys if none are provided.
  • Relies on helper functions (qontoApiRequest) to handle HTTP requests to the Qonto API.

Troubleshooting

  • Duplicate Transfers: If the same transfer is submitted multiple times, use the "Idempotency Key" property to prevent duplicates. If omitted, the node generates a new UUID each time, which may cause repeated transfers.
  • Invalid IBANs: Ensure that both debit and credit IBANs are valid and belong to supported countries/banks.
  • Currency Restrictions: Only EUR currency is currently supported for credit account currency and transfer currency. Using other currencies will likely result in API errors.
  • Attachment Issues: Attachments must be provided as base64-encoded binary data referenced by their binary property names. Incorrect or missing binary data will cause failures.
  • Authentication Errors: Verify that the selected authentication method is correctly configured in n8n with valid credentials.
  • API Rate Limits: Be aware of Qonto API rate limits; excessive requests may lead to throttling or temporary blocking.

Links and References

Discussion