Actions45
- Attachment Actions
- Beneficiary Actions
- Business Account Actions
- Card Actions
- Client Actions
- Client Invoice Actions
- Credit Note Actions
- External Transfer Actions
- Insurance Contract Actions
- Internal Transfer Actions
- Label Actions
- Membership Actions
- Organization Actions
- Quote Actions
- Request Actions
- SEPA Transfer Actions
- Statement Actions
- Supplier Invoice Actions
- Team Actions
- Transaction Actions
Attachment → Get One
AI-generatedOverview
This node integrates with the Qonto API to retrieve data related to various financial resources. Specifically, for the Attachment resource with the Get One operation, it fetches a single attachment by its unique ID. This is useful when you need to access or process a specific document or file linked to your Qonto account, such as invoices, receipts, or other financial attachments.
Practical examples include:
- Automatically downloading an invoice attachment for bookkeeping.
- Retrieving a receipt image to attach to an expense report.
- Accessing contract documents stored as attachments in Qonto.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Qonto API. Currently supports: API Key. |
| ID | The unique identifier of the attachment resource to retrieve. This is required. |
Output
The node outputs JSON data representing the requested attachment resource. The structure typically includes metadata about the attachment such as its ID, name, type, size, and possibly URLs or encoded content depending on the API response.
If the attachment contains binary data (e.g., a PDF or image), the node may provide this as binary output, allowing further processing or saving within n8n workflows.
Dependencies
- Requires an API key credential for authenticating requests to the Qonto API.
- The node uses the Qonto API endpoints, switching between sandbox and production environments based on configuration.
- No additional external dependencies are indicated beyond standard HTTP requests to Qonto's API.
Troubleshooting
Common issues:
- Invalid or missing attachment ID will cause errors; ensure the ID is correct and exists.
- Authentication failures if the API key is invalid or expired.
- Network timeouts or connectivity issues with the Qonto API.
Error messages:
"Unknown resource: attachment"— indicates a misconfiguration or typo in the resource parameter.- API error messages returned from Qonto (e.g., 401 Unauthorized) suggest checking API key validity.
- Timeout errors indicate network or server responsiveness problems; retry or check connectivity.
To resolve these, verify input parameters, confirm API credentials, and ensure stable internet connection.
Links and References
- Qonto API Documentation — official API reference for details on attachment resources and authentication.
- n8n documentation on creating custom nodes for further customization guidance.