Qonto

Consume Qonto API

Actions46

Attachment Actions
- Upload Attachment
- Show Attachment
Attachments in a Transaction Actions
Beneficiary Actions
Card Actions
Client Actions
Client Invoice Actions
Credit Note Actions
- Get a List of Credit Notes for an Organization
- Get Details of Credit Note for an Organization
External Transfer Actions
Insurance Contract Actions
Internal Transaction Actions
- Create Internal Transfer
Label Actions
- List Labels
- Show Label
Membership Actions
Organization Actions
- Get Organization and Its Bank_accounts
Request Actions
Statement Actions
- Show Statement
- List Statements
Supplier Invoice Actions
- Get a List of Supplier Invoices for an Organization
- Create Supplier Invoices with Attachments
Team Actions
- List Teams in an Organization
- Create a New Team
Transaction Actions
- List Transactions
- Show Transaction

Overview

This node interacts with the Qonto API to retrieve a list of supplier invoices for a specified organization. It allows users to filter invoices by payment status and creation date range, making it useful for financial management, accounting automation, or auditing workflows. For example, an accountant could use this node to fetch all pending supplier invoices created within the last month to review outstanding payments.

Properties

Name	Meaning
Authentication	Method of authentication to access the Qonto API. Options: "Login and Secret-Key", "OAuth2".
Organization ID	The unique identifier of the organization whose supplier invoices are to be fetched. (Required)
Status	Filter supplier invoices by their payment status. Options: "All", "Pending", "Paid".
Start Date	Fetch invoices created after this date.
End Date	Fetch invoices created before this date.

Output

The node outputs an array of supplier invoice objects in the json field. Each object represents a supplier invoice with details as returned by the Qonto API, such as invoice number, date, amount, currency, status, and any other metadata provided by the API.

No binary data output is produced by this operation.

Dependencies

Requires access to the Qonto API.
Requires either an API key credential ("Login and Secret-Key") or OAuth2 authentication configured in n8n.
No additional environment variables are explicitly required beyond standard n8n credential setup.

Troubleshooting

Common issues:
- Invalid or missing organization ID will cause the API request to fail.
- Incorrect authentication credentials or expired OAuth2 tokens will result in authorization errors.
- Filtering parameters (dates/status) must be valid; otherwise, the API may return empty results or errors.
Error messages:
- Authorization errors typically indicate invalid or missing API credentials; verify and update credentials.
- Validation errors on filters suggest incorrect date formats or unsupported status values; ensure inputs conform to expected formats.
- Network or API downtime errors require checking connectivity or Qonto service status.