Overview
This node acts as a trigger for events occurring in a bunq monetary account. It listens to specific types of notifications such as payments created or updated, card transactions, payment requests, and general mutations on the account. When one of the selected events happens, the node activates and outputs relevant data about that event.
Common scenarios where this node is useful include:
- Automating workflows when a new payment is received or updated.
- Monitoring card transactions for fraud detection or bookkeeping.
- Triggering follow-up actions when payment requests are created or updated.
- Reacting to any changes (mutations) on a specified monetary account.
For example, you could use this node to automatically log every new payment into a spreadsheet or notify your team via chat whenever a bunq.me payment is received.
Properties
| Name | Meaning |
|---|---|
| User ID | The ID of the user whose account to monitor. Leave empty to use the current authenticated user. |
| Account ID | The ID of the monetary account to monitor. This is required. |
| Event Types | The types of events to listen for. Options include: Payment Created, Payment Updated, Request Inquiry Created, Request Inquiry Updated, Card Transaction Created, bunq.me Payment, Mutation Created. Default is Payment Created. |
| Additional Options | A collection of optional filters and settings: - Include Raw Data: Whether to include the raw webhook payload in the output. - Filter Amounts: Minimum and/or maximum amount thresholds to filter triggering events. - Filter Description: Only trigger if the description contains specified text (case-insensitive). |
Output
The node outputs JSON data representing the event details when triggered. The structure includes:
event_type: The type of event that triggered the webhook.timestamp: When the event occurred.- Other event-specific fields such as amount, description, etc., depending on the event.
- Optionally, if enabled, the raw webhook payload under
raw_webhook_data.
If an error occurs during processing, the output will contain an error field with a message and the raw data received.
The node does not output binary data.
Dependencies
- Requires access to the bunq API with appropriate authentication credentials (e.g., OAuth2 or API key).
- Needs configuration of webhook URLs accessible by bunq to receive event notifications.
- Uses internal helper functions to format and request data from the bunq API.
Troubleshooting
- Webhook registration failure: If the node cannot create or verify the webhook URL with bunq, ensure the webhook URL is publicly accessible and the API credentials have sufficient permissions.
- No triggers firing: Verify that the correct User ID and Account ID are set, and that the selected event types match those generated by the account activity.
- Filtering issues: If no events pass filters, check that amount filters are correctly formatted as numbers and descriptions match case-insensitively.
- Error parsing webhook data: This may occur if bunq sends unexpected payloads; enabling raw data output can help diagnose issues.