Actions45
- Attachment Actions
- Beneficiary Actions
- Business Account Actions
- Card Actions
- Client Actions
- Client Invoice Actions
- Credit Note Actions
- External Transfer Actions
- Insurance Contract Actions
- Internal Transfer Actions
- Label Actions
- Membership Actions
- Organization Actions
- Quote Actions
- Request Actions
- SEPA Transfer Actions
- Statement Actions
- Supplier Invoice Actions
- Team Actions
- Transaction Actions
Overview
The node interacts with the Qonto API to retrieve multiple client records. Specifically, the "Client" resource with the "Get Many" operation allows users to fetch a list of clients from their Qonto account. This is useful for scenarios where you need to synchronize client data, generate reports, or perform bulk operations on client information.
For example, a user might want to pull all clients who match certain filters (like tax ID or email) or paginate through clients in batches to process them incrementally.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Qonto API. Only option available: "API Key". |
| Return All | Whether to return all matching clients or limit the number of results returned. |
| Limit | Maximum number of client records to return when "Return All" is false. Default and max: 100. |
| Page | The page number to retrieve when limiting results. Starts at 1. |
| Filters | Filter clients by tax ID, VAT number, email, or name using a string filter expression. |
Output
The output is an array of JSON objects representing client records retrieved from Qonto. Each object contains client details as provided by the Qonto API.
- The
jsonfield holds the client data. - If errors occur and "Continue On Fail" is enabled, error messages are included in the output JSON under an
errorproperty. - No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authentication with the Qonto API.
- The node uses the Qonto API base URL, which can switch between sandbox and production environments based on credentials configuration.
- Network connectivity to Qonto's API endpoints is necessary.
Troubleshooting
Common issues:
- Invalid or missing API key will cause authentication failures.
- Exceeding rate limits imposed by Qonto API may result in errors.
- Providing invalid filter strings may lead to no results or API errors.
- Requesting pages beyond available data returns empty results.
Error messages:
- Errors thrown by the API or network issues are surfaced as exceptions.
- When "Continue On Fail" is enabled, errors are returned in the output JSON with an
errormessage.
Resolutions:
- Verify that the API key is correct and has required permissions.
- Adjust filters to valid values.
- Use pagination parameters within valid ranges.
- Check network connectivity and API status.
Links and References
- Qonto API Documentation
- n8n documentation on Using API Key Credentials
