Actions46
- Attachment Actions
- Attachments in a Transaction Actions
- Beneficiary Actions
- Card Actions
- Client Actions
- Client Invoice Actions
- Credit Note Actions
- External Transfer Actions
- Insurance Contract Actions
- Internal Transaction Actions
- Label Actions
- Membership Actions
- Organization Actions
- Request Actions
- Statement Actions
- Supplier Invoice Actions
- Team Actions
- Transaction Actions
Overview
This node integrates with the Qonto API to create an internal transfer between two bank accounts within the same organization. It is useful for automating fund movements internally without involving external transfers, ensuring quick and secure money management between accounts.
Typical use cases include:
- Transferring funds between different company accounts.
- Automating internal bookkeeping by moving money from one IBAN to another.
- Ensuring idempotency in transfers to avoid duplicate transactions.
For example, a finance team can automate monthly budget allocations by creating internal transfers from the main account to various department accounts using this node.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to access the Qonto API. Options: "Login and Secret-Key", "OAuth2". |
| Idempotency Key | A unique string (recommended UUID) that identifies the transfer to prevent accidental duplicate submissions ("double spending"). This key must be unique per transfer. |
| Debit_iban | The IBAN of the account from which the amount will be debited (source account). |
| Credit_iban | The IBAN of the account to which the amount will be credited (destination account). |
| Reference | A text reference describing the transfer details, up to 140 characters. |
| Amount | The amount of money to transfer, expressed in the currency of the bank account. |
| Currency | The currency of the transfer amount. Only "EUR" is supported. |
Output
The node outputs JSON data representing the response from the Qonto API after creating the internal transfer. This typically includes details about the created transfer such as its ID, status, amounts, involved IBANs, timestamps, and any metadata returned by the API.
No binary data output is produced by this operation.
Dependencies
- Requires access to the Qonto API.
- Requires either an API key credential or OAuth2 authentication configured in n8n.
- Uses a UUID generator to create idempotency keys if not provided explicitly.
- The node depends on helper functions to make HTTP requests to the Qonto API.
Troubleshooting
- Duplicate Transfer Error: If the same idempotency key is reused, the API may reject the request or return the original transfer. Always generate a new unique idempotency key for each transfer.
- Invalid IBAN: Ensure that both debit and credit IBANs are valid and belong to accounts within the organization.
- Currency Mismatch: The currency must be "EUR"; other currencies are not supported and will cause errors.
- Authentication Failures: Verify that the chosen authentication method is correctly configured and has sufficient permissions.
- Missing Required Fields: All required properties (idempotency key, debit_iban, credit_iban, reference, amount, currency) must be provided; missing any will cause the API call to fail.
Links and References
- Qonto API Documentation - Internal Transfers
- UUID Generation (used internally for idempotency keys)