bunq icon

bunq

Interact with bunq banking API
Join our community

Actions42

Overview

This node operation updates an existing scheduled payment in the bunq banking system. Scheduled payments are recurring or future-dated payments set up to be executed automatically according to a defined schedule.

Use cases for this node include:

  • Modifying the status of a scheduled payment (e.g., pausing or cancelling it).
  • Changing the payment amount or description.
  • Updating the end date of the scheduled payment schedule.

Practical examples:

  • Pausing a monthly subscription payment temporarily.
  • Increasing the amount of a recurring rent payment.
  • Extending the duration of a scheduled donation by updating its end date.

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 scheduled payment is made.
Scheduled Payment ID The unique identifier of the scheduled payment to update.
Update Fields Collection of fields to update:
- Status New status of the scheduled payment. Options: Active, Paused, Cancelled
- Amount Updated payment amount as a string (currency assumed EUR).
- Description Updated description text for the scheduled payment.
- End Date Updated end date for the schedule (date/time format).

Output

The node outputs a JSON object representing the updated scheduled payment resource as returned by the bunq API. This typically includes details such as:

  • The updated status of the scheduled payment.
  • The new amount and currency.
  • Updated description.
  • Schedule information including start and end dates.
  • Identifiers and metadata related to the scheduled payment.

No binary data output is produced by this operation.

Dependencies

  • Requires access to the bunq banking API.
  • Requires valid API authentication credentials configured in n8n (an API key or OAuth2 token).
  • The node uses internal helper functions to make HTTP requests to the bunq API endpoints.

Troubleshooting

  • Common issues:

    • Invalid or missing Account ID or Scheduled Payment ID will cause the API request to fail.
    • Providing an invalid status value outside the allowed options will result in an error.
    • Incorrectly formatted dates for the end date field may cause request rejection.
    • Insufficient permissions or expired API credentials can lead to authorization errors.

  • Error messages:

    • Errors from the bunq API will be propagated, often indicating invalid parameters or unauthorized access.
    • If the scheduled payment ID does not exist, a "not found" error will occur.
    • Date parsing errors if the end date is not in ISO 8601 format.

  • Resolution tips:

    • Double-check all required IDs and ensure they correspond to existing resources.
    • Use only the allowed status values: ACTIVE, PAUSED, CANCELLED.
    • Format dates as ISO strings (e.g., YYYY-MM-DDTHH:mm:ssZ).
    • Verify API credentials and permissions before running the node.

Links and References

Discussion