bunq icon

bunq

Interact with bunq banking API
Join our community

Actions42

Overview

This node operation updates an existing card in the bunq banking system. It allows users to modify various attributes of a card such as its PIN code, activation code, status, and custom name. This is useful for scenarios where a user needs to manage their physical or virtual cards programmatically, for example:

  • Changing the PIN code after receiving a new card.
  • Activating a newly issued card using an activation code.
  • Updating the card's status to lost, stolen, deactivated, or expired.
  • Assigning a custom name to easily identify the card within the user's account.

Practical examples include automating card management workflows in financial applications, integrating card status updates into customer support systems, or bulk updating card details based on external triggers.

Properties

Name Meaning
User ID The ID of the user who owns the card. Leave empty to use the current authenticated user.
Card ID The unique identifier of the card to update. (Required)
Update Fields Collection of fields to update on the card:
- PIN Code New 4-digit PIN code for the card (string, password type).
- Activation Code Activation code for new cards (string).
- Status New status for the card. Options: ACTIVE, DEACTIVATED, LOST, STOLEN, EXPIRED.
- Card Name Custom name to assign to the card (string).

Output

The output is a JSON array containing the response from the bunq API after the update request. Each item corresponds to the updated card resource with its current state as returned by the API. The structure typically includes card details such as identifiers, status, limits, and other metadata.

No binary data is output by this operation.

Dependencies

  • Requires access to the bunq banking API.
  • Requires valid API credentials configured in n8n (an API key or OAuth2 token).
  • The node uses internal helper functions to format responses and make HTTP requests to the bunq API endpoints.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent Card ID will result in an error from the API.
    • Missing required fields like Card ID will cause the node to fail.
    • Incorrect PIN code format (not 4 digits) may be rejected by the API.
    • Attempting to update a card without proper permissions or with expired credentials will cause authentication errors.

  • Error messages:

    • Errors returned from the bunq API are passed through; typical messages include "Card not found", "Invalid PIN code", or "Unauthorized".
    • If the node throws an error about missing parameters, verify that all required inputs are provided.
    • Network or connectivity issues will manifest as request failures; ensure the API endpoint is reachable.

  • Resolution tips:

    • Double-check the Card ID and User ID values.
    • Ensure the API credentials are valid and have sufficient permissions.
    • Validate input formats before running the node.
    • Use the "Continue On Fail" option in n8n to handle individual errors gracefully in batch operations.

Links and References

Discussion