Overview
This node integrates with the Qonto API to retrieve client invoices. It is designed primarily to fetch multiple client invoices based on various filters and sorting options. This functionality is useful for financial automation workflows where users need to access invoice data from Qonto, such as generating reports, syncing invoices with other accounting systems, or triggering actions based on invoice status.
A practical example would be a workflow that automatically retrieves all unpaid client invoices created within a specific date range and then sends reminders to clients.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use: "API Key" or "OAuth2". |
Note: Although the node supports selecting the resource and operation, for this summary only the default resource and operation are relevant (clientInvoice - getMany), which are not exposed in the provided properties JSON but are part of the node's internal configuration.
Output
The node outputs an array of JSON objects representing client invoices retrieved from Qonto. Each item corresponds to one client invoice with its associated fields as returned by the Qonto API.
If an error occurs during execution and the node is configured to continue on failure, the output will include an object with an error field containing the error message.
No binary data output is produced by this node.
Dependencies
- Requires valid Qonto API credentials, either via an API key or OAuth2 token.
- The node dynamically selects the base URL depending on the environment specified in the credentials (sandbox or production).
- No additional external dependencies beyond standard HTTP requests authenticated with the provided credentials.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrect filter values (e.g., invalid dates or statuses) may result in empty responses or API errors.
- Rate limiting by the Qonto API could cause request failures; the node uses pagination with a delay to mitigate this.
Error messages:
- Errors thrown by the API or network issues will appear in the node’s error output if "Continue On Fail" is enabled.
- Typical error messages include authentication errors, invalid parameters, or connectivity problems.
Resolution tips:
- Verify that the correct authentication method and credentials are configured.
- Ensure filter parameters conform to expected formats.
- Check network connectivity and API availability.
- Use the "Return All" option carefully to avoid large data loads that might time out.
Links and References
- Qonto API Documentation
- n8n documentation on HTTP Request Node for understanding request handling and authentication setup.