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 manage various financial resources. Specifically, for the Attachment resource and the Show Attachment operation, it retrieves detailed information about a specific attachment by its ID. This is useful when you need to obtain metadata or download URLs for attachments related to transactions, invoices, or other financial documents stored in Qonto.
Common scenarios include:
- Fetching an attachment's details to display or process it further.
- Automating workflows that require access to specific document attachments.
- Integrating Qonto attachments into other systems or storage solutions.
Example: You have an attachment ID from a transaction and want to get its download URL or metadata to archive it or send it via email.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Qonto API. Options: "Login and Secret-Key", "OAuth2". |
| ID | The unique identifier of the attachment to retrieve details for (e.g., download URL). |
Output
The node outputs a JSON object containing the details of the requested attachment. This typically includes metadata such as filename, size, type, creation date, and URLs for downloading the attachment.
If the attachment contains binary data, the node provides access to this data encoded appropriately (e.g., base64), allowing further processing or saving.
Dependencies
- Requires valid authentication credentials for Qonto API, either via login and secret key or OAuth2.
- The node uses internal helper functions to make HTTP requests to Qonto's REST API.
- No additional external dependencies beyond those bundled with the node.
Troubleshooting
- Invalid or missing attachment ID: Ensure the "ID" property is correctly set and corresponds to an existing attachment in Qonto.
- Authentication errors: Verify that the provided API credentials are correct and have sufficient permissions.
- Network or API errors: Check connectivity and Qonto API status; handle rate limits or temporary outages.
- Error messages: The node throws errors if the API request fails; enabling "Continue On Fail" allows partial processing of multiple items.
Links and References
- Qonto API Documentation (for detailed API endpoints and attachment handling)
- n8n documentation on creating custom nodes