bunqInstall

Overview

The node interacts with the bunq banking API to manage scheduled payments for monetary accounts. Specifically, the Scheduled Payment - List operation retrieves a list of scheduled payment entries associated with a specified monetary account and optionally filtered by status or schedule type.

This operation is useful when you want to:

• Retrieve all scheduled payments for an account to review upcoming automatic transactions.
• Filter scheduled payments by their current status (e.g., active, paused) or by how often they recur (once, daily, weekly, etc.).
• Limit the number of results returned or fetch all available scheduled payments.

Practical example:
A user wants to monitor all active monthly scheduled payments on their primary checking account to ensure no unexpected recurring payments are set up. They can use this node operation to list those scheduled payments filtered by "Active" status and "Monthly" schedule type.

Properties

Output

The output is a JSON array where each item represents a scheduled payment entry retrieved from the bunq API. Each entry contains details about the scheduled payment such as amount, currency, recipient alias, description, schedule start and end times, recurrence unit, and status.

If multiple items are returned, they are aggregated into the output array.

No binary data is produced by this operation.

Dependencies

• Requires access to the bunq banking API via an API key credential configured in n8n.
• The node uses internal helper functions to make authenticated HTTP requests to bunq endpoints.
• No additional external services are required beyond the bunq API.

Troubleshooting

• Common issues:

  • Missing or invalid Account ID will cause the request to fail since it is required.
  • If the user does not have permission to access the specified monetary account, the API will return an authorization error.
  • Providing invalid filter values (e.g., unsupported status or schedule type) may result in empty responses or errors.

• Error messages:

  • Errors from the bunq API are propagated and typically include HTTP status codes and messages indicating the problem (e.g., 401 Unauthorized, 404 Not Found).
  • If the node throws an error about missing parameters, verify that the required fields like Account ID are correctly set.
  • Network or connectivity issues will cause request failures; ensure the API credentials are valid and network access is available.

Links and References

• bunq API Documentation - Scheduled Payments
• n8n Documentation - Creating Custom Nodes
• bunq Developer Portal