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 provides integration with the Qonto API, specifically allowing users to interact with various Qonto resources. For the Business Account resource and the Get Many operation, the node fetches multiple business account records from Qonto.
This operation is useful when you want to retrieve a list of business accounts associated with your Qonto organization, for example, to display them in a dashboard, synchronize them with another system, or perform bulk processing.
Practical examples:
- Fetch all business accounts to generate a report on account balances.
- Retrieve a limited number of business accounts for quick lookup or validation.
- Use the data as input for further automation workflows involving financial operations.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Qonto API. Only option available: "API Key". |
| Return All | Whether to return all business account results or only up to a specified limit (not shown in properties but implied by usage). |
Output
The output consists of an array of JSON objects representing business accounts retrieved from Qonto. Each item corresponds to one business account with its details as provided by the Qonto API.
If the node supports binary data output (not indicated here), it would typically represent attachments or documents related to business accounts, but this operation focuses on JSON data.
Dependencies
- Requires a valid API key credential for authenticating requests to the Qonto API.
- The node uses the Qonto API endpoints, switching between sandbox and production environments based on configuration.
- No additional external dependencies are indicated beyond the Qonto API access.
Troubleshooting
Common issues:
- Invalid or missing API key will cause authentication failures.
- Network timeouts or connectivity issues may prevent fetching data.
- Requesting too many records without enabling "Return All" might result in partial data.
Error messages:
"Unknown resource: businessAccount"— indicates a misconfiguration or typo in the resource parameter.- API errors returned from Qonto (e.g., unauthorized, rate limits) will be propagated; ensure credentials and permissions are correct.
Resolutions:
- Verify that the API key is correctly configured and has necessary permissions.
- Check network connectivity and endpoint URLs.
- Use the "Return All" property judiciously to avoid large data loads causing timeouts.
Links and References
- Qonto API Documentation
- n8n documentation on creating custom nodes