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 interacts with the bunq banking API to manage webhook notifications for monetary accounts. Specifically, the Webhook - List operation retrieves a list of webhook notification URLs associated with a specified monetary account. This is useful for users who want to monitor or audit webhook configurations linked to their bank accounts.
Common scenarios include:
- Auditing all webhook URLs registered on a specific monetary account.
- Integrating with external systems that require knowledge of existing webhook endpoints.
- Automating monitoring or management of webhook subscriptions.
Example: A user wants to fetch all webhook URLs configured for their primary monetary account to verify which services are receiving transaction updates.
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 for which to list webhooks. (Required) |
| Return All | Whether to return all webhook results or only up to a given limit. |
| Limit | Maximum number of webhook results to return if "Return All" is false. Range: 1 to 200. |
Output
The output is an array of JSON objects representing webhook notification URLs (notification filters) associated with the specified monetary account. Each object contains details about the webhook such as its ID, target URL, event types it listens to, and other metadata.
The output structure corresponds to the bunq API's webhook notification filter resource, formatted by the node’s internal response formatter.
No binary data 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 make HTTP requests to the bunq API and format responses.
Troubleshooting
- Missing or invalid Account ID: The operation requires a valid monetary account ID. Ensure this property is set correctly.
- API Authentication errors: Verify that the API credentials are properly configured and have sufficient permissions.
- Empty results: If no webhooks are returned, confirm that webhooks are actually configured for the specified account.
- Limit exceeded: When not using "Return All," ensure the limit is within allowed bounds (1-200).
- Network or API errors: Check network connectivity and bunq API status.