Qonto

Overview

This node integrates with the Qonto API, a financial platform for business banking. It allows users to perform a wide range of operations related to banking and financial management such as managing external transfers, beneficiaries, attachments, labels, memberships, organizations, transactions, internal transfers, requests, invoices, credit notes, clients, teams, statements, insurance contracts, and cards.

Common scenarios where this node is beneficial include automating payment workflows, managing client and supplier invoices, handling bank transactions, uploading and managing attachments, and administrating organizational resources like teams and memberships.

For example, a user can automate the creation of external transfers with idempotency keys to avoid duplicate payments, list transactions filtered by status or date, upload attachments to transactions, or create virtual cards with specific spending limits.

Properties

Note: The node also supports selecting a Resource and Operation, but since only the default resource and operation were requested, those are not detailed here.

Output

The node outputs JSON data representing the response from the Qonto API for the requested operation. The structure varies depending on the resource and operation invoked, typically including details such as IDs, statuses, dates, amounts, and other relevant financial or organizational information.

If multiple items are returned (e.g., listing resources), the output is an array of objects. For single item retrievals or creations, the output is a single object.

Binary data can be uploaded (e.g., attachments or PDFs), but the node does not output binary data; it only sends binary data encoded in base64 to the API.

Dependencies

• Requires an active Qonto account and access to the Qonto API.
• Requires either:
  • An API key credential (referred to as "Login and Secret-Key" authentication).
  • OAuth2 credentials for authentication.
• Uses UUID generation for idempotency keys to ensure safe retries of POST requests.
• Relies on helper functions (qontoApiRequest and handleListing) for making HTTP requests and handling pagination/listing.

Troubleshooting

• Authentication errors: Ensure that the correct authentication method is selected and valid credentials are provided.
• Idempotency key conflicts: When creating resources, idempotency keys are used to prevent duplicates. If you receive errors related to idempotency, verify that unique keys are generated or explicitly set.
• Missing required parameters: Many operations require specific parameters (e.g., IDs, IBANs). Double-check that all required inputs are provided.
• API rate limits or network issues: These may cause request failures. Implement retry logic or check network connectivity.
• Invalid filters or parameters: Filters must match expected formats; otherwise, the API may reject requests.

Links and References

• Qonto API Documentation
• n8n Documentation on Creating Custom Nodes