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
This node integrates with the Qonto API to list client invoices for a specified organization. It allows users to retrieve client invoices filtered by payment status and creation date range. This is useful for financial teams or accounting software integrations that need to fetch and process invoice data programmatically.
Typical use cases include:
- Fetching all client invoices for an organization to generate reports.
- Retrieving only pending or paid invoices to track outstanding payments.
- Filtering invoices created within a specific date range for auditing or reconciliation purposes.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to access the Qonto API: either "Login and Secret-Key" or "OAuth2". |
| Organization ID | The unique identifier of the organization whose client invoices are to be fetched. |
| Status | Filter client invoices by their payment status. Options: "All", "Pending", "Paid". |
| Start Date | Fetch invoices created after this date (inclusive). |
| End Date | Fetch invoices created before this date (inclusive). |
Output
The node outputs an array of client invoice objects in the json output field. Each object represents a client invoice retrieved from the Qonto API, containing details such as invoice number, invoice date, due date, amount, currency, description, and payment status.
No binary data output is produced by this operation.
Dependencies
- Requires valid authentication credentials for the Qonto API, either via login and secret key or OAuth2.
- The node depends on the Qonto API service being accessible.
- No additional environment variables or n8n configurations beyond standard credential setup are required.
Troubleshooting
Common issues:
- Invalid or missing organization ID will cause the API request to fail.
- Incorrect authentication credentials will result in authorization errors.
- Date filters must be valid ISO date strings; invalid dates may cause unexpected results or errors.
Error messages:
- Authorization errors typically indicate incorrect or expired credentials; re-authenticate or update credentials.
- Validation errors from the API may occur if required parameters are missing or malformed; verify input properties.
- Network or connectivity errors suggest issues reaching the Qonto API endpoint; check network settings and API availability.
Links and References
- Qonto API Documentation – Official API docs for detailed information on client invoices and other resources.