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 updates an existing webhook notification filter in the bunq banking API. Webhooks are used to receive real-time notifications about specific events related to a monetary account, such as mutations (transactions) or payments. Updating a webhook allows you to change the URL where notifications are sent and/or modify which event types trigger notifications.
Common scenarios for this node include:
- Changing the destination URL of an existing webhook after migrating your notification handling service.
- Adjusting the types of events you want to listen for without creating a new webhook.
- Managing webhook subscriptions programmatically as part of an automated workflow.
Example use case: You have a webhook set up to notify your system when payments are created, but now you want to also receive notifications for card transactions. Using this update operation, you can add the "Card Transaction Created" event type to the webhook's subscription.
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 associated with the webhook. |
| Webhook ID | The ID of the webhook notification filter to update. |
| Update Fields | Collection of fields to update on the webhook: |
| - Notification Target URL | The updated URL where webhook notifications will be sent. |
| - Event Types | List of event types to listen for. Options include: Payment Created, Payment Updated, Request Inquiry Created, Request Inquiry Updated, Card Transaction Created, bunq.me Payment, Mutation Created. |
Output
The output is a JSON object representing the updated webhook notification filter as returned by the bunq API. It typically includes details such as the webhook ID, the notification target URL, the subscribed event types, and other metadata.
No binary data output is produced by this operation.
Dependencies
- Requires access to the bunq banking API.
- Requires valid API credentials configured in n8n for authentication.
- The node uses internal helper functions to format API responses and handle pagination if needed.
Troubleshooting
- Missing or invalid Account ID or Webhook ID: The operation requires both the monetary account ID and the webhook ID. Ensure these are correctly provided; otherwise, the API will return an error.
- Invalid Notification Target URL: If the URL is malformed or unreachable, the API may reject the update request.
- Empty Event Types list: Providing an empty list of event types might disable all notifications. Confirm that at least one event type is selected.
- API Authentication errors: Verify that the API credentials are valid and have sufficient permissions to update webhooks.
- Network issues: Connectivity problems can cause request failures; check network settings and retry.
If the node throws an error, it usually contains the message from the bunq API response, which helps identify the issue.