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 interacts with the Qonto API to retrieve a list of credit notes for a specified organization. It allows users to filter credit notes by their status (all, pending, or used) and by creation date range (start and end dates). This functionality is useful for financial teams or accounting automation workflows that need to monitor, report on, or process credit notes issued within an organization.
Practical examples include:
- Fetching all credit notes created in the last month to reconcile accounts.
- Retrieving only pending credit notes to follow up on outstanding credits.
- Filtering credit notes by a specific date range for audit or reporting purposes.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with the Qonto API: either "Login and Secret-Key" or "OAuth2". |
| Organization ID | The unique identifier of the organization whose credit notes are to be fetched. |
| Status | Filter credit notes by their status. Options: "All", "Pending", "Used". |
| Start Date | Fetch credit notes created after this date (inclusive). |
| End Date | Fetch credit notes created before this date (inclusive). |
Output
The node outputs an array of credit note objects in the json output field. Each object represents a credit note retrieved from the Qonto API and includes details such as its status, creation date, and other relevant metadata as provided by the API.
No binary data output is produced by this operation.
Dependencies
- Requires access to the Qonto API.
- Requires valid authentication credentials configured in n8n, either via an API key credential or OAuth2 token.
- No additional external dependencies beyond the Qonto API and n8n's HTTP request capabilities.
Troubleshooting
Common issues:
- Invalid or missing organization ID will cause the API request to fail.
- Incorrect authentication setup may result in authorization errors.
- Date filters must be valid ISO date strings; invalid dates can cause request failures.
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; ensure all required fields are correctly set.
- Network or connectivity errors suggest issues reaching the Qonto API endpoint; verify network access and API availability.
Links and References
- Qonto API Documentation – Official API docs for detailed information on credit notes and other resources.
- n8n Documentation – For guidance on setting up credentials and using nodes.