bunqInstall

Overview

The node interacts with the bunq banking API, specifically supporting operations on various resources including users, monetary accounts, payments, transactions, request inquiries, cards, attachments, bunq.me payment links, webhooks, scheduled payments, and exports/statements.

For the bunq.me resource with the Get operation, the node retrieves details of a specific bunq.me payment link associated with a monetary account. This is useful for scenarios where you want to fetch information about a particular payment link created via bunq.me, such as its status, description, or transaction results.

Practical example:
You have a bunq.me payment link ID and want to programmatically check its current state or retrieve details about payments made through it. Using this node, you can specify the user (or leave empty for the current user), the monetary account ID, and the bunq.me ID to get the relevant data.

Properties

Output

The output is a JSON array containing the formatted response from the bunq API for the requested bunq.me payment link. The structure typically includes details such as:

• Payment link metadata (e.g., description, status)
• Associated monetary account information
• Transaction or fundraiser results related to the bunq.me link

The exact fields depend on the bunq API response but are wrapped in a consistent format by the node's internal formatter.

No binary data output is produced for this operation.

Dependencies

• Requires an active connection to the bunq API using either an OAuth2 or API key credential configured in n8n.
• The node uses internal helper functions to make HTTP requests to the bunq API endpoints.
• No additional external dependencies beyond the bunq API and n8n environment.

Troubleshooting

• Common issues:

  • Invalid or missing Account ID or bunq.me ID will cause the API request to fail.
  • If the user ID is specified incorrectly or does not have access to the monetary account, the request may return authorization errors.
  • Network connectivity or authentication token expiration can cause request failures.

• Error messages:

  • Errors returned from the bunq API will be propagated. For example, "Not Found" if the bunq.me ID does not exist.
  • Authentication errors if credentials are invalid or expired.
  • NodeOperationError indicating the statement or resource was not found or not ready (in other operations).

• Resolution tips:

  • Verify that the Account ID and bunq.me ID are correct and accessible.
  • Ensure the API credentials are valid and have sufficient permissions.
  • Check network connectivity and retry if transient errors occur.

Links and References

• bunq API Documentation – Official API docs for detailed endpoint info.
• bunq.me Payment Links – Overview of bunq.me payment links and usage.
• n8n Documentation – For configuring credentials and using custom nodes.