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
The node interacts with the "Request Inquiry" resource of the bunq banking API, specifically supporting the List operation. This operation retrieves payment request inquiries associated with a specified monetary account and optionally a user.
This node is useful for scenarios where you want to programmatically fetch payment requests made to or from a particular account, such as:
- Displaying all outstanding payment requests for reconciliation.
- Automating follow-ups on pending payment requests.
- Integrating payment request data into financial dashboards or reporting tools.
For example, you can list all payment requests for a given monetary account to monitor incoming requests or track which requests have been fulfilled.
Properties
| Name | Meaning |
|---|---|
| User ID | The ID of the user. If left empty, the current authenticated user is used by default. |
| Account ID | The ID of the monetary account for which to list payment requests. (Required) |
| Return All | Whether to return all results or only up to a given limit. |
| Limit | Maximum number of results to return if "Return All" is false. Range: 1 to 200. Default: 50. |
Output
The output is an array of JSON objects representing payment request inquiries retrieved from the bunq API. Each object corresponds to a single payment request inquiry and contains details such as amount, currency, counterparty information, description, status, and timestamps.
The exact structure follows the bunq API's response format but is normalized/formatted by the node before output.
No binary data is produced by this operation.
Dependencies
- Requires access to the bunq banking API via appropriate credentials (an API key or OAuth2 token).
- The node uses internal helper functions to make authenticated HTTP requests to the bunq API endpoints.
- No additional external services are required beyond the bunq API itself.
Troubleshooting
- Missing or invalid Account ID: Since the Account ID is required, omitting it or providing an incorrect value will cause the API call to fail. Ensure the correct monetary account ID is provided.
- Authentication errors: If the API credentials are missing, expired, or invalid, the node will fail to authenticate with the bunq API. Verify that valid credentials are configured in n8n.
- API rate limits or connectivity issues: Network problems or exceeding bunq API rate limits may cause request failures. Check network connectivity and bunq API usage policies.
- Empty results: If no payment requests exist for the specified account, the output will be an empty array.
- Limit vs Return All: Setting "Return All" to false but specifying a very high limit above 200 will be capped at 200 due to API constraints.