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 interacts with the Qonto API to retrieve multiple credit notes. Specifically, the "Get Many" operation under the "Credit Note" resource fetches a list of credit notes based on user-defined filters and pagination options. This is useful for financial workflows where users need to aggregate or analyze multiple credit notes, such as accounting automation, auditing, or reporting.
Practical examples include:
- Retrieving all credit notes created within a specific date range.
- Fetching a limited number of recent credit notes for review.
- Paginating through credit notes when dealing with large datasets.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication; currently supports "API Key". |
| Return All | Whether to return all available credit notes or limit the results. |
| Limit | Maximum number of credit notes to return (1 to 100). Only used if "Return All" is false. |
| Page | Page number to retrieve, starting at 1. Only used if "Return All" is false. |
| Filters | Collection of filters to narrow down results: |
| - Created From | Minimum creation date of credit notes to retrieve. |
| - Created To | Maximum creation date of credit notes to retrieve. |
Output
The output consists of an array of JSON objects, each representing a credit note retrieved from the Qonto API. Each object contains the credit note's data fields as returned by the API, such as identifiers, amounts, dates, and related metadata.
If binary data were involved (e.g., attachments), it would be included in a separate binary property, but this operation focuses on JSON data only.
Dependencies
- Requires access to the Qonto API via an API key credential.
- The node expects the Qonto environment to be configured (sandbox or production) which affects the base URL.
- No additional external dependencies beyond the Qonto API and proper authentication.
Troubleshooting
- Common Issues:
- Invalid or missing API key will cause authentication failures.
- Requesting pages beyond the available range may return empty results.
- Using date filters incorrectly (e.g., invalid date formats) might result in errors or no data.
- Error Messages:
- Errors from the API are propagated; typical messages include authentication errors or rate limiting.
- If the resource or operation is unknown, the node throws an error indicating the unknown resource.
- Resolutions:
- Ensure the API key is valid and has necessary permissions.
- Verify date filter formats and logical ranges.
- Use pagination parameters correctly to avoid empty responses.