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
This node integrates with the Qonto API to retrieve detailed information about a specific Credit Note by its ID. It is useful in scenarios where you need to fetch and process financial documents related to credit notes within your accounting or bookkeeping workflows. For example, you might use this node to automatically pull credit note details for reconciliation, auditing, or reporting purposes.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with the Qonto API. Currently supports: API Key. |
| ID | The unique identifier of the Credit Note resource you want to retrieve. This is required. |
Output
The node outputs JSON data representing the retrieved Credit Note object from the Qonto API. This JSON typically includes all relevant fields of the credit note such as amounts, dates, status, linked invoices, and other metadata defined by Qonto's API.
No binary data output is produced by this operation.
Dependencies
- Requires an active Qonto account with API access.
- Requires configuration of an API key credential in n8n to authenticate requests.
- The node uses Qonto’s official API endpoints, switching between sandbox and production environments based on credential settings.
Troubleshooting
Common issues:
- Invalid or missing Credit Note ID will cause the API call to fail.
- Incorrect or expired API key authentication will result in authorization errors.
- Network connectivity problems can cause timeouts or request failures.
Error messages:
"Unknown resource: creditNote"— indicates the resource name was not recognized; ensure the resource parameter is set correctly.- API error messages returned in the JSON under an
errorfield ifcontinueOnFailis enabled.
Resolutions:
- Verify the Credit Note ID is correct and exists in your Qonto account.
- Confirm that the API key credential is valid and has necessary permissions.
- Check network connectivity and endpoint URLs (sandbox vs production).
Links and References
- Qonto API Documentation – Official API reference for understanding Credit Note objects and endpoints.
- n8n Documentation – General guidance on using credentials and configuring nodes.
