Bunq Trigger
AI-generatedSummary
Starts a workflow when bunq sends a webhook callback for the selected category. It registers a bunq notification filter pointing at the node's n8n webhook URL when the workflow is activated, and removes it when the workflow is deactivated.
Inputs
- Callback Category (required) — The bunq event category to subscribe to, such as MUTATION (the default), PAYMENT, REQUEST, BILLING, CARD_TRANSACTION_SUCCESSFUL, CARD_TRANSACTION_FAILED, CHAT, DRAFT_PAYMENT, IDEAL, SOFORT, OAUTH, SCHEDULE_RESULT, SCHEDULE_STATUS, SHARE, SUPPORT, TAB_RESULT or BUNQME_TAB.
- bunqApi credential (required) — The bunq API credential (API key, public key, private key, environment). The node uses it to open a session and sign requests when it manages the notification filter.
Output shape
One item per received POST, containing the raw JSON body that bunq sent to the webhook, as sent by bunq. The node does not reshape it.
The webhook responds immediately on receipt (responseMode onReceived). Category filtering happens on the bunq side, so the node does not check the payload itself. On activation, the node first reads the existing bunq notification filters and merges the new category and URL into them, so other filters are kept. If it can't read the existing filters, activation fails instead of overwriting them. It re-checks that the filter was saved and retries once. On deactivation, it removes every filter whose target is this node's webhook URL, whatever its category. Deactivation errors are ignored. bunq API calls are rate-limited client-side.
Examples
Example 1: Run a workflow whenever a balance-changing event occurs on a bunq account.
Callback Category = Mutation, with a bunqApi credential. Activate the workflow so the filter is registered.
Example 2: Send an alert when a card payment is declined.
Callback Category = Card Transaction Failed. Connect the output to a Slack or Email node.
Example 3: React to incoming payment requests.
Callback Category = Request. Use the webhook body fields in later nodes.