Actions42
- Attachment Actions
- Payment Actions
- Transaction Actions
- Request Inquiry Actions
- Card Actions
- bunq.me Actions
- Webhook Actions
- Scheduled Payment Actions
- Export/Statement Actions
- User Actions
- Monetary Account Actions
Overview
This node interacts with the bunq banking API to perform various operations related to cards, including retrieving card limits. Specifically, the Card - Get Limits operation fetches the spending limits set on a particular card. This is useful for monitoring or auditing card usage restrictions.
Common scenarios where this node is beneficial include:
- Automatically checking card limits before processing transactions.
- Integrating card limit data into financial dashboards or reports.
- Alerting users if their card limits are approaching thresholds.
Example: A workflow could use this node to get the current daily and monthly spending limits of a corporate card to ensure compliance with company policies.
Properties
| Name | Meaning |
|---|---|
| User ID | The ID of the user owning the card. Leave empty to use the current authenticated user. |
| Card ID | The unique identifier of the card whose limits you want to retrieve. (Required) |
Output
The output JSON contains the details of the card limits retrieved from the bunq API. It typically includes information such as:
- Types of limits (e.g., daily limit, monthly limit).
- Limit amounts and their currencies.
- Status or metadata related to the limits.
The exact structure mirrors the bunq API response for card limits, formatted for easier consumption in n8n workflows.
No binary data is output by this operation.
Dependencies
- Requires an active connection to the bunq API via configured credentials (an API key or OAuth2 token).
- The node uses internal helper functions to make HTTP requests to the bunq API and format responses.
- No additional external services beyond bunq are required.
Troubleshooting
- Missing or invalid Card ID: The operation requires a valid card ID. Ensure the Card ID property is correctly set.
- Authentication errors: If the API credentials are incorrect or expired, the request will fail. Verify your bunq API credentials.
- API rate limits or connectivity issues: Network problems or bunq API rate limiting can cause failures. Retry after some time or check network access.
- Empty User ID: Leaving User ID empty defaults to the current authenticated user. If accessing another user's card, provide the correct User ID.
Error messages returned by the bunq API are passed through; reading these carefully helps identify issues like permission denials or invalid parameters.