Actions46
- Attachment Actions
- Attachments in a Transaction Actions
- Beneficiary Actions
- Card Actions
- Client Actions
- Client Invoice Actions
- Credit Note Actions
- External Transfer Actions
- Insurance Contract Actions
- Internal Transaction Actions
- Label Actions
- Membership Actions
- Organization Actions
- Request Actions
- Statement Actions
- Supplier Invoice Actions
- Team Actions
- Transaction Actions
Overview
The "List Memberships" operation of the Qonto node retrieves a list of memberships associated with the authenticated account. This operation is useful for scenarios where you need to manage or audit user memberships within an organization, such as fetching all employees or accountants who have access to the organization's resources.
Practical examples include:
- Displaying all current members in an organization's dashboard.
- Synchronizing membership data with another system.
- Auditing user roles and access permissions.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use: either "Login and Secret-Key" or "OAuth2". |
| Return All | Boolean flag indicating whether to return all memberships or limit the number of results. |
| Limit | Maximum number of memberships to return if "Return All" is false (minimum 1, default 50). |
Output
The output is a JSON array containing membership objects retrieved from the Qonto API. Each object represents a membership record with details such as email, first name, last name, role, team ID, and other membership-related information.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Qonto API.
- Requires valid authentication credentials configured in n8n, either via an API key credential or OAuth2 token.
- Uses internal helper functions to handle API requests and pagination.
Troubleshooting
- Common issues:
- Authentication errors due to invalid or expired credentials.
- API rate limits being exceeded.
- Network connectivity problems preventing API calls.
- Error messages:
- Errors returned from the Qonto API will be propagated, such as unauthorized access or invalid parameters.
- If the node is set to continue on failure, errors will be included in the output array with their message.
- Resolutions:
- Verify that the API credentials are correctly configured and have necessary permissions.
- Check network connectivity and retry after some time if rate limited.
- Ensure input parameters like "Limit" are within allowed ranges.