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
Attachments in a Transaction → Upload Attachment to a Transaction
AI-generatedOverview
This node uploads a binary attachment file to a specific transaction in the Qonto system. It is useful for scenarios where users need to associate documents, receipts, or other files with financial transactions for record-keeping or auditing purposes. For example, uploading an invoice PDF or a receipt image to a transaction to maintain comprehensive transaction records.
Use Case Examples
- Uploading a receipt image to a transaction to keep proof of purchase.
- Attaching an invoice PDF to a transaction for accounting purposes.
Properties
| Name | Meaning |
|---|---|
| Authentication | Selects the authentication method to use for the API request (Login and Secret-Key or OAuth2). |
| Transaction ID | The unique identifier of the transaction to which the attachment will be uploaded. |
| Attachments Binary | The name of the binary property in the input data that contains the file to be uploaded as an attachment. |
Output
JSON
success- Indicates whether the attachment upload was successful.message- A message confirming the successful upload of the attachment.transaction_id- The ID of the transaction to which the attachment was uploaded.uploaded_at- Timestamp of when the attachment was uploaded.
Dependencies
- Qonto API
Troubleshooting
- Ensure the 'Transaction ID' is valid and corresponds to an existing transaction in Qonto.
- Verify that the binary property name provided contains valid binary data to upload.
- Check that the authentication credentials are correctly configured and have the necessary permissions.
- Common error messages may include authentication failures, invalid transaction IDs, or issues with the binary data format. Resolving these typically involves verifying credentials, transaction existence, and input data integrity.