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 user-related operations. Specifically, for the User resource and List operation, it retrieves a list of users associated with the authenticated account. This is useful in scenarios where you want to fetch all users or a subset of users from your bunq account for further processing, reporting, or automation workflows.
Practical examples include:
- Fetching all users linked to an account to display or process their details.
- Retrieving a limited number of users for quick checks or summaries.
- Integrating user data into other systems or dashboards.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all user results or only up to a specified limit. |
| Limit | Maximum number of user results to return (only applicable if "Return All" is false). |
- Return All: If set to
true, the node will fetch all available users without limitation. - Limit: When "Return All" is
false, this property limits the number of users returned. The value must be between 1 and 200, defaulting to 50.
Output
The output is a JSON array where each item represents a user object formatted according to the bunq API response structure. Each user object contains detailed information about the user as provided by the bunq API.
The node does not output binary data for this operation.
Example output snippet (simplified):
[
{
"id": 12345,
"displayName": "John Doe",
"publicUuid": "uuid-string",
"avatar": { /* avatar details */ },
"status": "ACTIVE",
// ... other user fields
},
{
"id": 67890,
"displayName": "Jane Smith",
"publicUuid": "uuid-string",
"avatar": { /* avatar details */ },
"status": "ACTIVE",
// ... other user fields
}
]
Dependencies
- Requires access to the bunq banking API.
- Requires proper authentication credentials configured in n8n (an API key or OAuth2 token).
- Uses internal helper functions to make HTTP requests to the bunq API and format responses.
Troubleshooting
- Common issues:
- Authentication errors due to missing or invalid API credentials.
- Network connectivity problems preventing access to the bunq API.
- Exceeding API rate limits imposed by bunq.
- Error messages:
- Errors thrown by the node typically contain the message from the bunq API or network layer.
- If the node fails to retrieve users, verify that the API credentials are correct and have sufficient permissions.
- If requesting too many users without "Return All" enabled, ensure the "Limit" is within allowed bounds (1-200).