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 associated with monetary accounts. Specifically, the Delete Webhook operation removes a webhook notification filter identified by its ID from a specified monetary account of a user. This is useful for users who want to stop receiving certain webhook notifications or clean up obsolete webhook configurations.

Practical examples:

  • Automatically removing webhook URLs that are no longer in use.
  • Managing webhook subscriptions dynamically based on application logic.
  • Cleaning up webhook filters when closing or changing monetary accounts.

Properties

Name Meaning
User ID The ID of the user. If left empty, the current authenticated user is used.
Account ID The ID of the monetary account from which the webhook will be deleted. (Required)
Webhook ID The ID of the webhook notification filter to delete. (Required)

Output

The output is a JSON array containing the response from the bunq API after deleting the webhook. The structure typically includes confirmation of deletion or an empty response indicating success. No binary data is involved in this operation.

Example output JSON snippet:

[
  {
    "Response": []
  }
]

Dependencies

  • Requires access to the bunq banking API.
  • Requires an API authentication token or OAuth2 credentials configured in n8n to authorize requests.
  • The node uses internal helper functions to format responses and handle API requests.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent Webhook ID will result in an error from the bunq API.
    • Missing or incorrect Account ID can cause the request to fail.
    • Insufficient permissions or expired API credentials may lead to authorization errors.

  • Error messages:

    • Errors returned by the bunq API will be propagated. For example, "Webhook not found" indicates the specified webhook ID does not exist.
    • Authorization errors suggest checking API credentials and permissions.

  • Resolution tips:

    • Verify that the User ID, Account ID, and Webhook ID are correct and correspond to existing resources.
    • Ensure the API credentials are valid and have the necessary scopes.
    • Use the "Get" or "List" operations first to confirm webhook IDs before attempting deletion.

Links and References

Discussion