bunqInstall

Overview

The node enables uploading file attachments to the bunq banking API, specifically linking files as attachments to various financial objects such as payments, payment requests, or transactions. This operation is useful for adding supporting documents like receipts, invoices, or any relevant files to bunq records for better tracking and documentation.

Typical use cases include:

• Uploading a PDF invoice to a specific payment.
• Attaching an image (JPEG/PNG) of a receipt to a transaction.
• Adding CSV or JSON files as attachments for bookkeeping purposes.

Properties

Output

The output is a JSON object representing the response from the bunq API after uploading the attachment. It includes details about the created attachment resource, such as its ID, URLs, and metadata.

If the upload is successful, the node also performs an HTTP PUT request to upload the actual binary file data to a public URL provided by the API.

No binary data is outputted by this node; it only returns metadata about the uploaded attachment.

Dependencies

• Requires an active connection to the bunq API with appropriate credentials (an API key or OAuth2 token).
• The node uses internal helper functions to perform HTTP requests and handle binary data.
• The binary file to upload must be available in the workflow's binary data under the specified property name.

Troubleshooting

• Common issues:

  • Specifying a wrong or missing binary property name will cause the node to fail because it cannot find the file data.
  • Incorrect or missing user ID may lead to authorization errors if the current user context is not valid.
  • Providing an invalid or unsupported content type might cause the API to reject the upload.
  • Linking the attachment to a non-existent payment/request/transaction ID will result in an error.

• Error messages:

  • Errors from the bunq API are propagated and typically indicate issues like unauthorized access, invalid parameters, or resource not found.
  • If the statement that the attachment upload is not ready or failed, check the binary data and content type settings.

• Resolution tips:

  • Ensure the binary data exists and the property name matches exactly.
  • Verify user permissions and correct user ID usage.
  • Use "Auto Detect" content type when unsure, so the node infers the MIME type automatically.
  • Confirm the linked context IDs exist and belong to the user.

Links and References

• bunq API Documentation - Attachments
• n8n Documentation - Working with Binary Data
• MIME Types Reference