bunq icon

bunq

Interact with bunq banking API
Join our community

Actions42

Overview

This node interacts with the bunq banking API to manage webhook notification filters for monetary accounts. Specifically, the "Webhook" resource with the "Get" operation retrieves details of a specific webhook notification filter by its ID. This is useful when you want to fetch configuration or status information about a webhook that listens for events (such as account mutations) on a particular monetary account.

Practical examples:

  • Retrieve the details of a webhook to verify its event subscriptions and target URL.
  • Use the webhook data to audit or debug notification setups in your automation workflows.
  • Integrate with other systems by fetching webhook configurations dynamically before processing events.

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. (Required)
Webhook ID The ID of the webhook notification filter to retrieve. (Required)

Output

The output is a JSON object representing the webhook notification filter's details as returned by the bunq API. It typically includes information such as:

  • The webhook's unique identifier.
  • The notification target URL.
  • The categories and event types the webhook subscribes to.
  • Whether it applies to all monetary accounts.
  • Other metadata related to the webhook configuration.

No binary data is output by this operation.

Dependencies

  • Requires an active connection to the bunq API via an API key or OAuth2 token configured in n8n credentials.
  • The node uses internal helper functions to make HTTP requests to the bunq API endpoints.
  • Proper permissions on the bunq account are necessary to access webhook information.

Troubleshooting

  • Missing Required Parameters: If Account ID or Webhook ID is not provided, the node will fail. Ensure these are set correctly.
  • Authentication Errors: Invalid or expired API credentials will cause authentication failures. Refresh or reconfigure credentials as needed.
  • Webhook Not Found: If the specified webhook ID does not exist under the given account, the API will return an error. Verify the webhook ID and account ID.
  • Permission Denied: Insufficient permissions on the bunq account may prevent access to webhook data.
  • Network Issues: Connectivity problems can cause request timeouts or failures.

Links and References

Discussion