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, allowing users to perform various banking-related operations programmatically. Specifically, for the User - Get operation, it retrieves information about a user from the bunq system. If a specific User ID is provided, it fetches that user's details; if left empty, it fetches the current authenticated user's information.
Common scenarios where this node is beneficial include:
- Automating retrieval of user profile data for integration with other systems.
- Fetching user details dynamically in workflows without manual intervention.
- Building dashboards or reports that require up-to-date user information from bunq.
Example use case:
- A workflow that triggers on a schedule to get the current user's profile and updates an internal CRM system with the latest contact details.
Properties
| Name | Meaning |
|---|---|
| User ID | The ID of the user to retrieve. Leave empty to get the current authenticated user. |
Output
The output is a JSON array containing the user data retrieved from the bunq API. The structure corresponds to the user object as returned by the bunq API, formatted by the node's internal response formatter. This typically includes user details such as name, email, status, and other profile-related information.
No binary data output is produced by this operation.
Dependencies
- Requires access to the bunq API via appropriate credentials (an API key or OAuth2 token).
- The node uses internal helper functions to make HTTP requests to the bunq API endpoints.
- Proper configuration of the bunq API credentials within n8n is necessary for authentication.
Troubleshooting
- Empty or invalid User ID: If a non-existent User ID is provided, the API may return an error or empty response. Ensure the User ID is correct or leave it empty to fetch the current user.
- Authentication errors: If credentials are missing or invalid, the node will fail to connect to the bunq API. Verify that the API key or OAuth2 credentials are correctly set up.
- API rate limits or downtime: The bunq API might throttle requests or be temporarily unavailable. In such cases, retry after some time or check bunq's service status.
- Malformed responses: If the API response format changes, the node's internal formatter might fail. Updating the node or checking for newer versions could resolve this.