Qonto

Overview

This node enables uploading attachments to a specific transaction within the Qonto financial platform. It is useful when you want to associate documents such as receipts, invoices, or any relevant files directly with a transaction record for better bookkeeping and audit trails.

Typical use cases include:

• Automatically attaching scanned receipts to expense transactions.
• Uploading invoice PDFs linked to payment transactions.
• Adding supporting documentation to bank statement entries.

For example, after retrieving a transaction ID, you can upload an image or PDF file as an attachment to that transaction, ensuring all related data is stored together in Qonto.

Properties

Output

The node outputs a JSON object representing the response from the Qonto API after uploading the attachment. This typically includes metadata about the newly created attachment such as its ID, filename, and possibly URLs or references.

No binary output is produced by this operation; the uploaded file is sent as base64 encoded content within the request.

Dependencies

• Requires valid authentication credentials for Qonto API access, either via an API key (login and secret-key) or OAuth2 token.
• Uses the n8n helper method to retrieve binary data from the specified input property and convert it to base64 encoding.
• Generates a unique idempotency key for each upload request to ensure safe retries without duplicate uploads.

Troubleshooting

• Missing or incorrect binary property name: If the specified binary property does not exist or is empty, the upload will fail. Ensure the input data contains the correct binary field with valid file data.
• Invalid transaction ID: Providing an incorrect or non-existent transaction ID will cause the API to return an error. Verify the transaction ID before uploading.
• Authentication errors: Using invalid or expired credentials will result in authorization failures. Confirm that the API key or OAuth2 token is valid and has necessary permissions.
• Idempotency key conflicts: Although unlikely, if the generated idempotency key collides with a previous request, the API may reject the upload. This is mitigated by using UUID v4 keys.

Common error messages usually come directly from the Qonto API and should be interpreted accordingly, e.g., "Transaction not found", "Unauthorized", or "Invalid file format".

Links and References

• Qonto API Documentation - Attachments
• n8n Documentation - Working with Binary Data
• UUID v4 Specification