Qonto

Overview

This node interacts with the Qonto API to manage attachments related to transactions. Specifically, the "Remove an Attachment From a Transaction" operation allows users to delete a specific attachment from a given transaction in their Qonto account.

Common scenarios where this node is beneficial include:

• Automating cleanup of outdated or incorrect attachments linked to financial transactions.
• Managing document storage by programmatically removing unnecessary files.
• Integrating with workflows that require dynamic management of transaction-related documents.

For example, a user might use this node to remove a mistakenly uploaded invoice attachment from a transaction after detecting an error in the document.

Properties

Note: Although the provided properties JSON only shows id, the code references both transaction_id and attachment_id parameters for this operation. Typically, to remove an attachment from a transaction, both the transaction's ID and the attachment's ID are required. The user should ensure these inputs are provided accordingly.

Output

The output is a JSON array containing the response from the Qonto API after attempting to remove the specified attachment. The structure depends on the API's DELETE endpoint response but generally confirms successful deletion or provides error details.

No binary data output is involved in this operation.

Dependencies

• Requires access to the Qonto API.
• Requires valid authentication credentials, either via Login and Secret-Key or OAuth2.
• The node uses helper functions to make HTTP requests to the Qonto API.
• No additional external services or environment variables are explicitly required beyond the API credentials.

Troubleshooting

• Missing or invalid IDs: If the transaction ID or attachment ID is missing or incorrect, the API will likely return an error indicating the resource was not found. Ensure both IDs are correctly provided.
• Authentication errors: Using invalid or expired credentials will cause authentication failures. Verify that the API key or OAuth token is valid and has necessary permissions.
• Permission issues: The authenticated user must have rights to modify the transaction and its attachments.
• API rate limits: Excessive requests may trigger rate limiting; handle such errors by retrying after some delay.
• Error messages: The node throws errors returned by the Qonto API. Reading the error message can guide resolution, e.g., "Attachment not found" means the attachment ID does not exist for the given transaction.

Links and References

• Qonto API Documentation — Official API docs for managing transactions and attachments.
• n8n Documentation — For general guidance on using n8n nodes and handling credentials.