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 operation allows you to create scheduled payments using the bunq banking API. Scheduled payments are automated transfers set to execute at specified intervals (once, daily, weekly, monthly, or yearly) starting from a defined date and optionally ending on a certain date.
Common scenarios where this node is beneficial include:
- Automating recurring bill payments such as rent, utilities, or subscriptions.
- Setting up regular transfers to savings accounts or other users.
- Scheduling one-time future payments for planned expenses.
For example, you can schedule a monthly payment of 100 EUR to a recipient's IBAN account starting from the first day of next month, with an optional end date after 12 months.
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 the payment will be made. |
| Amount | The amount to transfer (e.g., "10.00"). |
| Currency | The currency of the payment. Options: EUR, USD, GBP. |
| Counterparty Type | The type of recipient identifier. Options: IBAN (bank account), Email, Phone number. |
| IBAN | The IBAN of the recipient (required if Counterparty Type is IBAN). |
| The email address of the recipient (required if Counterparty Type is Email). | |
| Phone | The phone number of the recipient (required if Counterparty Type is Phone). |
| Recipient Name | The name of the recipient. |
| Description | Payment description or reference text. |
| Schedule Type | How often the payment should be executed. Options: Once, Daily, Weekly, Monthly, Yearly. |
| Start Date | When to start executing the scheduled payment (date and time). |
| End Date | When to stop executing the scheduled payment (optional; applicable for recurring schedules). |
Output
The output is a JSON array containing the response from the bunq API formatted into a simplified structure. Each item represents the created scheduled payment entry with details such as payment amount, currency, recipient information, schedule timing, and status.
No binary data output is produced by this operation.
Dependencies
- Requires access to the bunq banking API via an API key or OAuth2 token configured in n8n credentials.
- The node uses internal helper functions to make HTTP requests to the bunq API endpoints.
- Proper permissions on the bunq account to create scheduled payments are necessary.
Troubleshooting
- Missing required fields: Ensure all mandatory properties like Account ID, Amount, Currency, Recipient Name, and appropriate counterparty details (IBAN/Email/Phone) are provided.
- Invalid dates: The Start Date must be a valid ISO date/time string. If End Date is provided, it must be later than Start Date.
- API errors: Errors returned from the bunq API (e.g., insufficient funds, invalid account) will be thrown. Check the error message for details.
- Authentication issues: Verify that the API credentials are correctly set up and have sufficient permissions.
- Counterparty mismatch: Make sure the counterparty type matches the provided recipient detail (e.g., do not provide an email if counterparty type is IBAN).