bunq icon

bunq

Interact with bunq banking API
Join our community

Actions42

Overview

The node interacts with the bunq banking API to perform various operations related to banking resources. Specifically, for the Card resource with the Get operation, it retrieves detailed information about a specific card associated with a user.

This node is beneficial in scenarios where you need to programmatically access card details such as card status, limits, or other metadata within an automated workflow. For example, you might use this node to fetch card information before performing further actions like updating card settings or monitoring card usage.

Practical example:

  • Retrieve details of a specific card by its ID to verify its current status or attributes.
  • Use the card data to trigger notifications or audits in your financial workflows.

Properties

Name Meaning
User ID The ID of the user who owns the card. If left empty, the current authenticated user is used.
Card ID The unique identifier of the card to retrieve. This property is required for the Get operation.

Output

The output is a JSON object containing the detailed information of the requested card. The structure typically includes fields such as card identifiers, status, type, limits, and other card-specific metadata as returned by the bunq API.

No binary data output is produced by this operation.

Example output snippet (conceptual):

{
  "id": "12345",
  "status": "ACTIVE",
  "type": "MASTERCARD",
  "name_on_card": "John Doe",
  "limits": [
    {
      "type": "DAILY",
      "value": "1000.00",
      "currency": "EUR"
    }
  ],
  ...
}

Dependencies

  • Requires an active connection to the bunq banking API.
  • Needs appropriate API credentials configured in n8n (an API key or OAuth2 token).
  • The node uses internal helper functions to format responses and handle API requests.

Troubleshooting

  • Missing or invalid Card ID: Since the Card ID is required, ensure it is provided and correctly formatted. Errors will occur if this is missing or incorrect.
  • Authentication errors: Verify that the API credentials are valid and have sufficient permissions to access card data.
  • API rate limits or connectivity issues: Network problems or API limits may cause request failures; retry or check API status.
  • Empty User ID: If no User ID is provided, the node defaults to the current authenticated user. Ensure this matches your intended context.

Common error messages:

  • "Card not found": The specified Card ID does not exist or is inaccessible.
  • "Unauthorized": Authentication failed due to invalid credentials.
  • "Request failed": General network or API error; check connectivity and parameters.

Links and References

Discussion