bunq icon

bunq

Interact with bunq banking API

Actions42

Attachment → Delete

AI-generated

Overview

This node interacts with the bunq banking API to manage file attachments related to a user account. Specifically, the Attachment - Delete operation allows users to delete an existing attachment by its ID. This is useful for cleaning up or removing outdated or unwanted files linked to payments, transactions, or requests within the bunq system.

Practical examples:

  • Automatically deleting receipt images after processing them.
  • Removing obsolete documents attached to payment requests.
  • Managing storage by deleting large or unnecessary attachments programmatically.

Properties

Name Meaning
User ID The ID of the user whose attachment is targeted. Leave empty to use the current user.
Attachment ID The unique identifier of the attachment to delete. This is required.

Output

The output is a JSON object representing the response from the bunq API after attempting to delete the attachment. It typically contains confirmation details about the deletion operation.

Example structure (simplified):

{
  "Response": [
    {
      "AttachmentPublic": {
        // Details about the deleted attachment or confirmation message
      }
    }
  ]
}

No binary data is output by this operation.

Dependencies

  • Requires access to the bunq banking API.
  • Needs an API authentication token or OAuth2 credentials configured in n8n to authorize requests.
  • The node uses internal helper functions to format responses and handle API requests.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent Attachment ID will result in an error from the API.
    • Omitting the required Attachment ID property will cause the node to fail.
    • Insufficient permissions or expired API credentials can lead to authorization errors.
  • Error messages:

    • Errors returned by the bunq API will be propagated. For example, "Attachment not found" indicates the specified ID does not exist.
    • Network or authentication errors may occur if API keys are misconfigured or expired.
  • Resolutions:

    • Verify the Attachment ID is correct and exists.
    • Ensure API credentials are valid and have necessary permissions.
    • Check network connectivity and bunq API status.

Links and References

Discussion