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 manage scheduled payments. Specifically, the Scheduled Payment - Get operation retrieves details of a particular scheduled payment from a specified monetary account. This is useful for users who want to programmatically access information about their recurring or planned payments, such as verifying payment schedules, amounts, recipients, and statuses.
Practical examples:
- Fetching details of a scheduled rent payment to confirm the next payment date and amount.
- Retrieving information about a subscription payment set up via bunq to monitor upcoming charges.
- Integrating scheduled payment data into financial dashboards or accounting systems.
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 from which the scheduled payment belongs. (Required) |
| Scheduled Payment ID | The unique identifier of the scheduled payment to retrieve. (Required) |
Output
The output is a JSON object representing the detailed information of the requested scheduled payment. It includes fields such as:
- Payment amount and currency
- Recipient details (counterparty alias)
- Description of the payment
- Schedule details including start date, end date, recurrence unit, and size
- Status of the scheduled payment
The structure corresponds directly to the bunq API's scheduled payment entry response, formatted for easier consumption in n8n workflows.
No binary data is output by this operation.
Dependencies
- Requires an active connection to the bunq API using either an OAuth2 or API key credential configured in n8n.
- The node depends on helper functions to make HTTP requests to the bunq API and format responses.
- Proper permissions on the bunq account are necessary to access scheduled payment data.
Troubleshooting
- Missing or invalid Account ID or Scheduled Payment ID: The node requires these IDs to be valid and present; otherwise, the API call will fail. Ensure these values are correctly provided.
- Authentication errors: If the API credentials are incorrect or expired, the node will throw authentication errors. Verify that the API key or OAuth token is valid and has sufficient permissions.
- Scheduled payment not found: If the Scheduled Payment ID does not exist under the specified account, the API will return an error. Confirm the ID is correct and belongs to the given account.
- Network issues: Connectivity problems can cause request failures. Check network access and bunq API status.