Actions42
- Attachment Actions
- Payment Actions
- Transaction Actions
- Request Inquiry Actions
- Card Actions
- bunq.me Actions
- Webhook Actions
- Scheduled Payment Actions
- Export/Statement Actions
- User Actions
- Monetary Account Actions
Overview
This node operation interacts with the "Attachment" resource of the bunq banking API to list file attachments associated with a user. It allows retrieving metadata about attachments such as files linked to payments, transactions, or other objects within the bunq ecosystem.
Common scenarios where this node is beneficial include:
- Fetching all attachments for audit or record-keeping purposes.
- Filtering attachments by content type or size to find specific documents or images.
- Retrieving attachments created within a certain date range for compliance or reporting.
For example, a user might want to list all JPEG image attachments uploaded in the last month or retrieve all attachments smaller than a certain size.
Properties
| Name | Meaning |
|---|---|
| User ID | The ID of the user whose attachments are to be listed. Leave empty to use the current authenticated user. |
| Return All | Whether to return all matching attachments or limit the number of results. |
| Limit | Maximum number of attachments to return (only used if Return All is false). Range: 1 to 200. |
| Additional Fields | Optional filters to narrow down the list of attachments: |
| - Content Type | Filter attachments by MIME content type (e.g., "image/jpeg"). |
| - Size Min | Minimum file size in bytes. |
| - Size Max | Maximum file size in bytes. |
| - Created After | Only include attachments created after this date/time. |
| - Created Before | Only include attachments created before this date/time. |
Output
The output is an array of JSON objects representing attachment metadata retrieved from the bunq API. Each object contains details about an attachment, such as its ID, description, content type, size, creation date, and potentially links to the actual file URLs.
The node does not directly output binary data for attachments in this operation; it only lists metadata. To download or upload attachment files, other operations would be used.
Dependencies
- Requires connection to the bunq banking API.
- Needs appropriate API credentials configured in n8n for authentication.
- Uses internal helper functions to make HTTP requests and format responses.
Troubleshooting
- Empty results: Ensure the User ID is correct or left empty to default to the current user. Also verify that any filters (content type, size, dates) are set correctly and do not exclude all attachments.
- API errors: Check that the API credentials are valid and have permission to access attachments.
- Limit issues: If you expect more results but get fewer, verify whether "Return All" is enabled or the "Limit" property is set too low.
- Date filter format: Make sure date/time inputs are valid ISO strings or Date objects as expected by the node.