Qonto icon

Qonto

Consume Qonto API

Actions46

Overview

This node integrates with the Qonto API to create an external transfer from a specified bank account to a beneficiary. It is useful for automating payments or money transfers to external accounts, such as suppliers, contractors, or partners. By using this node, users can programmatically initiate transfers while ensuring idempotency to avoid duplicate transactions.

Practical examples include:

  • Automatically paying invoices by creating external transfers based on incoming data.
  • Scheduling future payments by specifying a scheduled date.
  • Attaching supporting documents to transfers for record-keeping and compliance.

Properties

Name Meaning
Authentication Method of authenticating with the Qonto API. Options: "Login and Secret-Key" or "OAuth2".
Idempotency Key A unique string (recommended UUID) that identifies the transfer request to prevent accidental duplicate transfers. This key ensures the same transfer is not processed multiple times.
Beneficiary ID The identifier of the beneficiary account to which the money will be sent. Typically corresponds to the IBAN of the recipient's account.
Debit IBAN The IBAN of the account from which the funds will be debited.
Reference A reference string describing the transfer, up to 140 characters. Useful for adding details about the payment purpose.
Note An optional note providing additional information about the transfer.
Currency The currency of the transfer amount. Must be "EUR" as per the API requirements.
Scheduled Date Optional date (YYYY-MM-DD) indicating when the transfer should be executed by Qonto. Allows scheduling payments in advance.
Amount The amount of money to transfer, expressed in the currency of the debit account.
Attachment IDs An array of attachments to add to the transfer, provided as binary data properties. Multiple attachments can be included by specifying their binary property names separated by commas.

Output

The node outputs a JSON object representing the created external transfer as returned by the Qonto API. This typically includes details such as transfer ID, status, amount, currency, beneficiary information, scheduled date, and any attached files metadata.

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

The node does not output binary data directly but supports attaching binary files to the transfer via input properties.

Dependencies

  • Requires access to the Qonto API.
  • Requires either an API key credential ("Login and Secret-Key") or OAuth2 authentication configured in n8n.
  • Uses the uuid library internally to generate idempotency keys if not provided.
  • Relies on helper functions (qontoApiRequest) to make HTTP requests to the Qonto API.

Troubleshooting

  • Duplicate Transfers: If you see errors related to duplicate transfers, ensure you provide a unique idempotency key for each distinct transfer request.
  • Invalid IBANs: Errors may occur if the beneficiary or debit IBANs are invalid or not recognized by Qonto. Double-check the IBAN formats.
  • Currency Restrictions: The API only accepts EUR currency for external transfers; using other currencies will cause errors.
  • Attachment Issues: Attachments must be provided as base64-encoded binary data. Ensure the binary property names are correct and data is properly formatted.
  • Authentication Failures: Verify that the selected authentication method is correctly configured and credentials are valid.
  • Scheduled Date Format: The scheduled date must be in YYYY-MM-DD format; incorrect formatting may lead to rejection.

Links and References

Discussion