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 interacts with the bunq banking API to perform various operations related to exporting account statements and data. Specifically, the "Get Statement" operation retrieves detailed information about a particular statement export for a specified monetary account. This is useful for users who want to programmatically access their bank statements or export data for accounting, auditing, or personal finance management.
Practical examples include:
- Automatically fetching monthly bank statements for bookkeeping.
- Integrating statement data into financial dashboards.
- Verifying statement details before triggering further automated workflows.
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 from which to retrieve the statement. (Required) |
| Statement ID | The ID of the specific statement export to retrieve. (Required) |
Output
The output JSON contains the detailed information of the requested statement export as returned by the bunq API. It typically includes metadata such as statement format, date range, status, creation time, and possibly URLs or identifiers related to the export.
If the statement is not found or an error occurs, the node will throw an error unless configured to continue on failure.
No binary data is output in this operation; the response is purely JSON-formatted statement metadata.
Dependencies
- Requires connection to the bunq banking API.
- Requires an API key credential or OAuth2 token configured in n8n for authentication.
- The node uses internal helper functions to make HTTP requests to the bunq API endpoints.
Troubleshooting
- Statement Not Found: If the provided Statement ID does not exist or is incorrect, the node will throw an error indicating the statement was not found.
- Authentication Errors: Ensure that the API credentials are correctly set up and have sufficient permissions to access the user's monetary accounts and exports.
- Empty User ID: Leaving the User ID empty defaults to the current authenticated user. If accessing another user's data, ensure proper authorization.
- Network Issues: Connectivity problems with the bunq API can cause request failures; verify network access and API availability.
- Continue On Fail: If enabled, errors will be captured in the output as error messages instead of stopping execution.