Qonto icon

Qonto

Interact with Qonto API

Actions45

Supplier Invoice → Get Many

AI-generated

Overview

The node interacts with the Qonto API to retrieve multiple supplier invoices based on user-defined filters and pagination options. It is useful for automating financial workflows, such as fetching batches of supplier invoices for review, accounting, or integration with other systems.

Typical use cases include:

  • Retrieving all supplier invoices within a specific date range.
  • Filtering invoices by their payment status (e.g., pending, paid).
  • Paginating through large sets of invoices to process them in manageable chunks.

For example, an accountant could use this node to automatically fetch all "Pending" supplier invoices created last month for reconciliation.

Properties

Name Meaning
Authentication Method of authentication; currently supports only "API Key".
Return All Whether to return all matching results or limit the output to a specified number.
Limit Maximum number of results to return when "Return All" is false; ranges from 1 to 100.
Page Page number to retrieve when limiting results; starts at 1.
Filters Collection of optional filters to narrow down results:
- Status Filter invoices by status; options: "To Review", "Pending", "Scheduled", "Paid".
- Created From Minimum creation date to filter invoices from.
- Created To Maximum creation date to filter invoices up to.

Output

The node outputs an array of JSON objects representing supplier invoices. Each object contains invoice details as returned by the Qonto API, such as invoice ID, status, creation date, amounts, and related metadata.

If binary data were involved (e.g., invoice attachments), it would be included in a separate binary property, but this operation focuses on JSON data retrieval only.

Dependencies

  • Requires an API key credential for authenticating requests to the Qonto API.
  • The node uses the Qonto API endpoint, which varies depending on whether the environment is set to sandbox or production.
  • No additional external dependencies are required beyond the API key and network access to Qonto's service.

Troubleshooting

  • Common issues:
    • Invalid or missing API key will cause authentication failures.
    • Requesting pages beyond available data may return empty results.
    • Using date filters in incorrect formats might lead to errors or no results.
  • Error messages:
    • Errors from the Qonto API (e.g., unauthorized, bad request) will be surfaced as error messages.
    • If the resource or operation is unknown, the node throws an explicit error.
  • Resolutions:
    • Verify that the API key is correctly configured and has necessary permissions.
    • Ensure date filters follow the expected ISO date-time format.
    • Use pagination parameters within allowed ranges.

Links and References

Discussion