bunqInstall

Overview

This node interacts with the bunq banking API to perform operations related to attachments. Specifically, the Attachment - Get operation retrieves details about a specific attachment associated with a user in the bunq system. This is useful when you want to fetch metadata or information about files linked to payments, transactions, or other objects within a user's account.

Practical examples include:

• Retrieving an invoice or receipt file attached to a payment.
• Accessing documents or images uploaded as attachments for bookkeeping or auditing.
• Fetching attachment details to display or process them further in an automation workflow.

Properties

Output

The output is a JSON object containing the details of the requested attachment. The structure typically includes metadata such as attachment ID, description, content type, size, creation date, and URLs to access the attachment content.

Example output JSON structure (simplified):

{
  "id": "string",
  "description": "string",
  "content_type": "string",
  "size": number,
  "created": "ISO8601 timestamp",
  "urls": {
    "public": "string"
  },
  "attached_object": {
    "id": "string",
    "type": "string"
  }
}

If the attachment includes binary data (e.g., a file), it is represented by URLs pointing to the location where the file can be accessed or downloaded.

Dependencies

• Requires an active connection to the bunq API via appropriate credentials (an API key or OAuth2 token).
• The node uses internal helper functions to format responses and make authenticated HTTP requests to the bunq API.
• No additional external dependencies beyond the bunq API and n8n's standard environment are needed.

Troubleshooting

• Common issues:

  • Providing an invalid or non-existent Attachment ID will result in an error from the bunq API indicating the resource was not found.
  • Omitting the required Attachment ID property will cause the node to fail validation before execution.
  • If the User ID is incorrect or the user does not have access to the specified attachment, the API may return authorization errors.
  • Network connectivity issues or expired/invalid API credentials will cause request failures.

• Error messages and resolutions:

  • "Attachment not found": Verify that the Attachment ID is correct and belongs to the specified or current user.
  • "Unauthorized" or "Forbidden": Check that the API credentials have sufficient permissions and are valid.
  • "Request failed" or network errors: Ensure stable internet connection and bunq API availability.

Links and References

• bunq API Documentation
• bunq Attachments API Reference
• n8n Documentation on Creating Custom Nodes