bunq icon

bunq

Interact with bunq banking API
Join our community

Actions42

Overview

The node interacts with the bunq banking API to list export statements for a specified monetary account. It allows users to retrieve multiple bank statement exports filtered by various criteria such as status, format, and creation date. This operation is useful for automating financial workflows where you need to access or process bank statements programmatically.

Common scenarios:

  • Automatically fetching recent bank statements in CSV or PDF format for accounting or auditing.
  • Filtering statements by their processing status (e.g., only completed exports).
  • Retrieving statements created within a specific date range for reconciliation purposes.

Practical example:
A user wants to download all completed PDF bank statements from their primary monetary account created in the last month to upload them into an accounting system.

Properties

Name Meaning
User ID The ID of the user. Leave empty to use the current authenticated user.
Account ID The ID of the monetary account to list statements for. (Required)
Return All Whether to return all matching statements or limit the number of results.
Limit Maximum number of statements to return if not returning all (1 to 200).
Filters Collection of filters to narrow down the list of statements:
   Status Filter by export status. Options: Pending, Processing, Completed, Failed.
   Format Filter by statement format. Options: CSV, PDF, MT940, CAMT053.
   Created After Only show statements created after this date/time.
   Created Before Only show statements created before this date/time.

Output

The output is a JSON array where each item represents an export statement object returned by the bunq API. Each object contains details about a statement export such as its ID, status, format, creation date, and potentially a download URL if available.

If the "downloadStatement" operation is used (not requested here but related), the node can also output binary data representing the actual statement file (e.g., PDF or CSV) under a configurable binary property.

Dependencies

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

Troubleshooting

  • Common issues:

    • Invalid or missing Account ID will cause the API request to fail.
    • Filtering with invalid dates or unsupported formats may result in empty responses or errors.
    • Requesting too many items without setting "Return All" may truncate results unexpectedly.

  • Error messages:

    • "Statement {id} is not ready for download. Status: {status}" — indicates trying to download a statement that is still processing or failed.
    • API authentication errors if credentials are incorrect or expired.

  • Resolutions:

    • Ensure the Account ID is correct and accessible by the authenticated user.
    • Use valid filter values and date formats.
    • Use "Return All" carefully to avoid large data loads.
    • Refresh or reconfigure API credentials if authentication fails.

Links and References

Discussion