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
The bunq.me Update operation allows you to modify an existing bunq.me payment link associated with a specific monetary account. This node action is useful when you want to change the status, description, redirect URL, or expiry time of a payment link after it has been created.
Typical use cases include:
- Cancelling a payment link that is no longer valid.
- Updating the description to provide more context or details.
- Changing the redirect URL where users are sent after completing payment.
- Extending or modifying the expiry time of the payment link.
For example, if you have a bunq.me payment link for collecting donations and want to close it early, you can update its status to "CANCELLED". Or if you want to update the message shown to payers, you can change the description dynamically.
Properties
| Name | Meaning |
|---|---|
| User ID | The ID of the user owning the monetary account. Leave empty to use the current user. |
| Account ID | The ID of the monetary account linked to the bunq.me payment link. (Required) |
| bunq.me ID | The ID of the bunq.me payment link to update. (Required) |
| Update Fields | Collection of fields to update on the bunq.me link: |
| - Status | New status of the bunq.me link. Options: WAITING_FOR_PAYMENT, CANCELLED |
| - Description | Updated description text for the payment link. |
| - Redirect URL | Updated URL to redirect payers after payment completion. |
| - Expiry Time | Updated expiry date/time for the payment link. |
Output
The output is a JSON array containing the updated bunq.me payment link object as returned by the bunq API. The structure reflects the bunq API response format for bunq.me resources, typically including fields such as the updated status, description, redirect URL, expiry time, and other metadata about the payment link.
No binary data is produced by this operation.
Dependencies
- Requires access to the bunq banking API.
- Requires proper 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
- Missing Required Fields: Ensure that
Account IDandbunq.me IDare provided; otherwise, the API call will fail. - Invalid Status Value: Only
WAITING_FOR_PAYMENTandCANCELLEDare accepted for the status field. Using other values will cause errors. - Expired or Invalid bunq.me ID: If the specified bunq.me ID does not exist or is expired, the API will return an error.
- Authentication Errors: Verify that your API credentials are valid and have sufficient permissions to update bunq.me links.
- Network Issues: Connectivity problems may cause request failures; check network settings and retry.
If the node throws an error, enabling "Continue On Fail" can help process multiple items without stopping the workflow.