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 creates a webhook notification subscription in the bunq banking API. It allows users to specify a target URL where bunq will send notifications about specific events related to monetary accounts. This is useful for automating workflows that need to react to banking events such as payments, transactions, or account mutations.
Common scenarios include:
- Automatically triggering processes when a payment is created or updated.
- Receiving real-time updates on card transactions or request inquiries.
- Monitoring multiple event types with a single webhook subscription.
For example, a business could use this node to create a webhook that notifies their system whenever a new payment is made to their account, enabling instant order processing.
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 to monitor. (Required) |
| Notification Target URL | The URL where bunq will send webhook notifications. (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, Card Transaction Failed, Card Transaction Successful. (Required) |
| Additional Fields | Optional extra settings: |
| - Category | The category of notifications: Mutation, Request, or Schedule. Defaults to Mutation. |
| - Include All Monetary Accounts | Whether to include notifications for all monetary accounts instead of just the specified one. Defaults to false. |
Output
The output is a JSON object representing the created webhook subscription as returned by the bunq API. It includes details such as the webhook ID, the notification target URL, the subscribed event types, and other metadata confirming the webhook creation.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the bunq API via an API key credential or OAuth2 token configured in n8n.
- The node uses internal helper functions to make HTTP requests to the bunq API endpoints.
- The user must have appropriate permissions on the specified monetary account to create webhooks.
Troubleshooting
- Missing Required Fields: If "Account ID", "Notification Target URL", or "Event Types" are missing, the API call will fail. Ensure these are provided.
- Invalid URL: The notification target URL must be reachable and accept incoming POST requests from bunq. Invalid URLs may cause webhook delivery failures.
- Permission Errors: Insufficient permissions on the monetary account can cause authorization errors.
- API Rate Limits: Frequent webhook creations might hit API rate limits; handle errors accordingly.
- Network Issues: Connectivity problems between n8n and bunq API or the notification target URL can cause failures.
Error messages typically come from the bunq API and should be reviewed to adjust parameters or credentials.