bunq icon

bunq

Interact with bunq banking API
Join our community

Actions42

Overview

The node interacts with the bunq banking API to perform various payment-related operations. Specifically, for the Payment - List operation, it retrieves a list of payments made from a specified monetary account. This is useful for scenarios where you want to fetch recent or all payment transactions associated with an account, such as generating reports, auditing transactions, or syncing payment data with other systems.

For example, you might use this node to:

  • Retrieve the last 50 payments made from a business account.
  • Fetch all payments for reconciliation purposes.
  • Integrate payment history into a CRM or accounting tool.

Properties

Name Meaning
User ID The ID of the user whose payments you want to list. Leave empty to use the current user.
Account ID The ID of the monetary account from which to list payments. (Required)
Return All Whether to return all payment results or only up to a given limit.
Limit Maximum number of payment results to return if "Return All" is false. Range: 1 to 200.

Output

The output is a JSON array where each item represents a payment object retrieved from the bunq API. Each payment object contains details about individual payments such as amount, currency, counterparty information, description, status, and timestamps.

The structure corresponds to the bunq API's payment response format but is normalized by the node’s internal formatting function for easier consumption in workflows.

No binary data is output by this operation.

Dependencies

  • Requires access to the bunq banking API.
  • Requires configuration of an API authentication credential (e.g., an API key or OAuth2 token) within n8n to authorize requests.
  • The node uses internal helper functions to make HTTP requests and format responses.

Troubleshooting

  • Common issues:

    • Missing or invalid Account ID will cause the request to fail since it is required.
    • If the user ID is incorrect or not authorized, the API may return authorization errors.
    • Requesting too many items without setting "Return All" to true may result in truncated results.

  • Error messages:

    • Errors from the bunq API (e.g., 401 Unauthorized, 404 Not Found) will be thrown and can be caught if "Continue On Fail" is enabled.
    • If the API rate limits are exceeded, the node may throw errors indicating too many requests.

  • Resolutions:

    • Ensure valid and authorized credentials are configured.
    • Verify that the Account ID and optionally User ID are correct.
    • Use "Return All" carefully to avoid large data loads; otherwise, set a reasonable limit.
    • Enable "Continue On Fail" to handle intermittent API errors gracefully.

Links and References

Discussion