bunqInstall

Overview

This node interacts with the bunq banking API to perform operations related to "Request Inquiry" resources, specifically supporting the "Get" operation in this context. The "Get" operation retrieves details of a specific payment request (request inquiry) associated with a monetary account and optionally a user.

Common scenarios where this node is beneficial include:

• Fetching detailed information about a particular payment request sent or received via bunq.
• Automating workflows that need to verify or process payment requests by retrieving their current status and details.
• Integrating bunq payment requests into broader financial or CRM systems for tracking and reconciliation.

Practical example:

• A business uses this node to fetch the status and details of a payment request by its ID to confirm if it has been paid before proceeding with order fulfillment.

Properties

Output

The output is a JSON object representing the requested payment request's details as returned by the bunq API. This typically includes fields such as amount, currency, counterparty alias, description, status, and other metadata related to the payment request.

The node does not output binary data for this operation.

Example output structure (simplified):

{
  "id": "string",
  "amount_inquired": {
    "value": "string",
    "currency": "string"
  },
  "counterparty_alias": {
    "type": "string",
    "value": "string",
    "name": "string"
  },
  "description": "string",
  "status": "string",
  ...
}

Dependencies

• Requires an active connection to the bunq API using either an OAuth2 token or API key credential configured in n8n.
• The node depends on helper functions to format API responses and handle pagination internally.
• No additional external dependencies beyond the bunq API and n8n environment are required.

Troubleshooting

• Missing Required Parameters: Ensure that both Account ID and Request ID are provided; otherwise, the API call will fail.
• Authentication Errors: Verify that the API credentials are correctly set up and have sufficient permissions to access the requested resource.
• Request Not Found: If the specified Request ID does not exist or does not belong to the given account/user, the API will return an error. Double-check IDs.
• Network Issues: Connectivity problems can cause request failures; ensure stable internet access.
• API Rate Limits: Excessive calls may be throttled by bunq; implement retry logic or reduce call frequency if needed.

Links and References

• bunq API Documentation - Request Inquiry
• n8n Documentation - Creating Custom Nodes
• bunq Developer Portal